Information recording medium, information recording/playback method, and information recording/playback apparatus

ABSTRACT

A digital stream signal complying with MPEG-TS is handled as stream object ESOB. The ESOB is recorded in unit of stream object unit ESOBU which includes one or more pack/packet groups. Each pack/packet group has a pack/packet group header at its head position, and stores one or more TS packets after the pack/packet group header.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority fromprior Japanese Patent Application No. 2003-083631, filed Mar. 25, 2003,the entire contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an information recordingmedium/information storage medium (or data structure), an informationrecording/playback method, and an information recording/playbackapparatus, which are suited to record/play back a digital stream signal(MPEG-TS) used in satellite digital TV broadcast or terrestrial digitalTV broadcast.

2. Description of the Related Art

In recent years, TV broadcast has entered the era of digital broadcastshaving Hi-Vision programs as principal broadcast contents. The currentdigital broadcast adopts an MPEG transport stream (to be abbreviated asMPEG-TS as needed hereinafter). In the field of digital broadcast usingmoving pictures, MPEG-TS will be used as a standard format in thefuture.

At the start of such digital TV broadcast, market needs for a streamerthat can directly record digital TV broadcast contents (withoutdigital/analog conversion) are increasing. As a currently, commerciallyavailable, typical streamer that directly records digital broadcast data(MPEG-TS or the like), a video cassette recorder (D-VHS streamer) namedD-VHS® is known.

Upon stream-recording digital broadcast data, MPEG-TS data of digitalbroadcast received by a tuner system (normally, a set-top box called anSTB) is input to a D-VHS streamer via an IEEE1394 cable. The streamerexecutes required encoding processes, and records the encoded data on aD-VHS tape. Note that IEEE1394 is the interface standard, whichspecifies exchange of commands and transmission/reception of data.

Upon playing back broadcast data, the D-VHS streamer reads recorded data(MPEG-TS data or the like) from the recorded D-VHS tape, and sends theread MPEG-TS data to a data expansion unit in the STB via the IEEE1394cable. In this way, the recorded data is played back.

Since the D-VHS streamer directly records the broadcasted bitstream on atape, a plurality of programs are multiplexed and recorded on the tape.For this reason, upon playback of the multiplexed recorded programs, theD-VHS streamer sends all data to the STB regardless of whether they areto be played back from the beginning or middle of a program. In thiscase, the user selects and plays back a desired one of a plurality ofmultiplexed recorded programs.

Since a tape is used as a recording medium, the D-VHS streamer can makesequential playback but cannot make a random access to the recordedcontents. For this reason, it is difficult to quickly jump to a desiredposition in the desired recorded program and to start playback from thatposition (difficulty of special playback).

In addition to D-VHS, in recent years, STBs that use hard disc drives(HDD) are put on the marker as a digital broadcast streamer. This STBsaves stream data in an HDD and realizes excellent random accessperformance. However, in this apparatus, the user cannot easily exchangethe HDD. For this reason, such apparatus is not suited to preserve alarge volume of recorded data as a library over a long term.

As a prevailing solution to the problems (difficulty of randomaccess/difficulty of special playback) of D-VHS, and that (difficulty ofmedia exchange) of the HDD, a currently, commercially available streamerthat uses large-capacity disc media such as a DVD-RAM and the like maybe used.

As an example of the “streamer using the DVD-RAM”, “Digital VideoRecording System” disclosed in Jpn. Pat. Appln. KOKAI Publication No.2000-268537 (patent reference 1) is known.

“Digital Video Recording System” disclosed in patent reference 1 ispremised on a specific streamer standard. As an example of this streamerstandard, the DVD stream recording standard (Version 1.0) developedFebruary of 2001 (although it is not open to the public) is known (but,no product using this standard is yet commercially available).

This streamer standard aims at scrambled contents and also broadcastcontents of various worldwide broadcast stations. For this reason, aminimum playback unit in video contents is defined by a data amount withreference to ECC blocks. For this reason, upon making special playback,even when data is read out from a target address, I-picture data thatcan be played back is not found, and the playback start position mayshift considerably. That is, it is very difficult for this standard toattain special playback.

The streamer standard has contents unsuitable for special playback.However, in patent reference 1 above, special playback is facilitated bymatching the head of a data unit (VOBU/SOBU) with that of I-picture data(paragraph 0117) or recording the head position of each I-picture datain a management area (paragraph 0118).

The streamer standard packetizes and records irrespective of contents tobe recorded. For this reason, upon playback, the arrival time of packetsthat store the recorded contents can be detected, but the playback timeof the recorded contents cannot be directly detected. Hence, it is noteasy for the user to designate the playback start position on a timebasis, and playback operations such as time search and the like areinconvenient.

As a disc recorder standard free from the above inconvenience (of timesearch and the like), the DVD video recording (DVD-VR) standard isknown, and many products based on this DVD video recording standard arecurrently commercially available. This video recording standard adoptstime map information. With this time map information (which is notavailable in the streamer standard), it is easy for the user todesignate the playback start position on a time basis.

However, the video recording standard is not compatible to streamrecording of digital TV broadcast (in order to record digital broadcastcontents using a recorder based on the video recording standard, ananalog video signal that has temporarily undergone D/A conversion issent from the STB to the analog video input of the recorder and isMPEG-encoded in the recorder again, and the encoded data is digitallyrecorded on a DVD-RAM disc or the like). Therefore, the existing videorecording standard cannot meet needs of users who want to air-checkdigital TV broadcast contents (especially, Hi-Vision programs) whilemaintaining their quality.

BRIEF SUMMARY OF THE INVENTION

An information medium to which the system of an embodiment of thepresent invention can be applied is configured to separately record dataof a digital stream signal as a plurality of objects (ESOB). Each object(ESOB) may include data units (ESOBU), each of which may be formed withreference to an integer number of groups of picture (GOP) or based ondata for integer seconds as a playback time. One data unit (ESOBU) maybe made up of pack/packet groups each of which may be formed by groupinga plurality of transport stream packets (TS packets). The pack/packetgroup may be formed of a pack/packet group header and pack/packet groupdata containing TS packets having data of the digital stream signal.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

FIG. 1 is a view for explaining the data structure according to anembodiment of the present invention;

FIG. 2 is a view for explaining the relationship among a playbackmanagement information layer, object management information layer, andobject layer in the data structure according to the embodiment of thepresent invention;

FIG. 3 is a view for explaining an example of the configuration of afield (RTR_VMGI/EHDVR_MGI) of one management information(RTR_VMG/EHDVR_MG) recorded on AV data management information recordingarea 130 shown in FIG. 1;

FIG. 4 is a view for explaining an example of the configuration ofanother field (ESFIT/ESTR_FIT) of one management information(RTR_VMG/EHDVR_MG) in the data structure according to the embodiment ofthe present invention;

FIG. 5 is a view for explaining an example of the configuration of thecontents of respective elements in the other field (ESFIT) of themanagement information shown in FIG. 4;

FIG. 6 is a view for explaining an example of the configuration ofobject information (one of ESOBI#1 to ESOBI#m) of the elements in otherfield (ESFIT) of the management information shown in FIG. 5;

FIG. 7 is a view for explaining an example of the configuration of somefields (MAP_Group_GI and MAP_ENT#1 to MAP_ENT#r) of map groupinformation (one of MAP_GroupI#1 to MAP_GroupI#n) contained in theobject information (ESOB#1) shown in FIG. 6;

FIG. 8 is a view for explaining an example of the configuration ofanother field (ESOBU_ENT#1 to ESOBU_ENT#q) of the map group information(one of MAP_Group#1 to MAP_Group#n) contained in the object information(ESOB#1) shown in FIG. 6;

FIG. 9 is a view for explaining an example of the contents ofinformation (PCR_Pack number or 1st_Ref_PIC_PTM), which is contained inanother field (ESOBU_ENT#1) of the map group information (MAP_Group#n)shown in FIG. 8 and is associated with the location of a program clockreference, depending on the availability of video and audio data;

FIG. 10 is a view for explaining an example of the configuration ofprogram chain information as one field of another management information(RTR_ESMG) recorded on AV data management information recording area 130shown in FIG. 1;

FIG. 11 is a view for explaining an example of the configuration of thecontents of respective elements of the program chain information shownin FIG. 10;

FIG. 12 is a view for explaining an example of the configuration of playlist information as another field of another management information(RTR_ESMG) recorded on AV data management information recording area 130shown in FIG. 1;

FIG. 13 is a view for explaining an example of the configuration of thecontents of respective elements of the play list information shown inFIG. 12;

FIG. 14 is a view for explaining an example of the configuration of adata unit (ESOBU) for a stream object shown in FIG. 1 or 2;

FIG. 15 is a view for explaining an example of the configuration of anarrival time (ATS) of a pack contained in a pack group header shown inFIG. 14;

FIG. 16 is a view for explaining an example of the configuration of copygeneration management information (or copy control information CCI)contained in the pack group header shown in FIG. 14;

FIG. 17 is a view for explaining an example of the configuration ofdisplay control information (DCI) contained in the pack group headershown in FIG. 14;

FIG. 18 is a view for explaining an example of the configuration of anincrement (IAPAT) of the packet arrival time contained in a pack groupshown in FIG. 14 after the pack group header;

FIG. 19 is a view for explaining an example of the configuration of PCRlocation information (PCR_Pack number or the like) contained in the packgroup header shown in FIG. 14;

FIG. 20 is a block diagram for explaining an example of an apparatus forrecording and playing back AV information (digital TV broadcast programand the like) on and from an information recording medium (optical disc,hard disc, or the like) using the data structure according to theembodiment of the present invention;

FIG. 21 shows an example of management information to be stored in AVdata management information recording area 130 shown in FIG. 1, and is aview for explaining the data structure as a combination of videorecording management information VMG and stream recording managementinformation ESMG;

FIG. 22 is a view for explaining an example of the configuration of thecontents of stream information (one of ESOBI_STI#1 to ESOBI_STI#m)contained in management information (ESFIT) shown in FIG. 21;

FIG. 23 is a view for explaining an example of the configuration of thecontents of video attribute information (V_ATR) contained in streaminformation shown in FIG. 22;

FIG. 24 is a flow chart (overall operation process flow) for explainingan example of the overall operation of the apparatus shown in FIG. 20;

FIG. 25 is a flow chart (interrupt process flow) for explaining anexample of an interrupt process in the operation of the apparatus shownin FIG. 20;

FIG. 26 is a flow chart (recording flow) for explaining an example of arecording operation (part 1) of the apparatus shown in FIG. 20;

FIG. 27 is a flow chart (recording flow) for explaining an example of arecording operation (part 2) of the apparatus shown in FIG. 20;

FIG. 28 is a flow chart (STI setting process flow) for explaining anexample of the contents of a stream information generation process(ST120) shown in FIG. 27;

FIG. 29 is a flow chart (buffer fetch process flow) for explaining anexample of the contents of a buffer fetch process (ST130) shown in FIG.27;

FIG. 30 is a flow chart (overall playback operation flow) for explainingan example of a playback operation (part 1) of the apparatus shown inFIG. 20;

FIG. 31 is a flow chart (overall playback operation flow) for explainingan example of a playback operation (part 2) of the apparatus shown inFIG. 20;

FIG. 32 is a flow chart (process flow upon cell playback) for explainingan example of a process upon cell playback (part 1) in the apparatusshown in FIG. 20;

FIG. 33 is a flow chart (process flow upon cell playback) for explainingan example of a process upon cell playback (part 2) in the apparatusshown in FIG. 20;

FIG. 34 is a view for explaining an example of the data structure of aprogram map table (PMT) that can be used by the apparatus shown in FIG.20;

FIG. 35 is a view showing an example of the contents of a digital copycontrol descriptor that can be used by the PMT shown in FIG. 34 and thelike (service description table SDT, event information table EIT, andthe like);

FIG. 36 is a view for explaining an application example of digital copycontrol to video data;

FIG. 37 is a view for explaining an application example of digital copycontrol to audio data;

FIG. 38 is a view showing an example of the contents of a componentdescriptor that can be used by the PMT shown in FIG. 34 and the like(event information table EIT and the like);

FIG. 39 is a view for explaining an example of the contents of componenttypes shown in FIG. 38;

FIG. 40 is a flow chart (overall transfer operation flow) for explainingan example of the overall data transfer operation (part 1) in theapparatus shown in FIG. 20;

FIG. 41 is a flow chart (overall transfer operation flow) for explainingan example of the overall data transfer operation (part 2) in theapparatus shown in FIG. 20;

FIG. 42 is a flow chart (process flow upon cell transfer) for explainingan example (part 1) of the process upon cell transfer (ST320) shown inFIG. 41;

FIG. 43 is a flow chart (process flow upon cell transfer) for explainingan example (part 2) of the process upon cell transfer (ST320) shown inFIG. 41; and

FIG. 44 is a flow chart (process flow upon time search) for explainingan example of a time search process (a search conducted based on aplayback time designated by the user) with respect to already recordedstream information of a digital TV broadcast program or the like in theapparatus shown in FIG. 20;

FIG. 45 is a view for explaining another example of the configuration ofa data unit (ESOBU) for the stream object (ESOB);

FIG. 46 is a view for explaining another example of the configuration ofmanagement information (EHDVR_MG) recorded on AV data managementinformation recording area 130 shown in FIG. 1;

FIG. 47 exemplifies contents of the extended video manager informationmanagement table (EVMGI_MAT) shown in FIG. 46;

FIG. 48 exemplifies contents of the extended play list search pointer(EPL_SRP) shown in FIG. 46;

FIG. 49 exemplifies contents of the play list resume marker information(EPL_SRP) shown in FIG. 46;

FIG. 50 exemplifies contents of the extended movie AV file informationtable (EM_AVFIT) shown in FIG. 46;

FIG. 51 exemplifies contents of the extended movie video object generalinformation (EM_VOB_GI) shown in FIG. 50;

FIG. 52 exemplifies contents of the extended video object time mapgeneral information (EVOB_TMAP_GI) shown in FIG. 50;

FIG. 53 exemplifies contents of the extended still picture AV fileinformation table (ES_AVFIT) shown in FIG. 46;

FIG. 54 exemplifies contents of the extended stream file informationtable (ESTR_FIT) shown in FIG. 46;

FIG. 55 exemplifies contents of the extended stream object information(ESOBI) shown in FIG. 54;

FIG. 56 exemplifies contents of the extended stream object informationgeneral information (ESOBI_GI) shown in FIG. 55;

FIG. 57 exemplifies contents of the extended stream object type(ESOB_TY) shown in FIG. 56;

FIG. 58 exemplifies contents of the copy control information(CP_CTRL_INFO) shown in FIG. 56;

FIG. 59 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for video ES) shown in FIG. 55;

FIG. 60 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for audio ES) shown in FIG. 55;

FIG. 61 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for other ES) shown in FIG. 55;

FIG. 62 exemplifies contents of stream type information (ES_TY) shown ineach of FIGS. 59 to 61;

FIG. 63 exemplifies contents of the video attribute information (V_ATR)shown in FIG. 59;

FIG. 64 exemplifies contents of the audio attribute information (A_ATR)shown in FIG. 60;

FIG. 65 exemplifies contents of the grouping information generalinformation (GPI_GI) shown in FIG. 55;

FIG. 66 exemplifies contents of the elementary stream packet identifier(ES_PID) shown in FIG. 55;

FIG. 67 exemplifies contents of the extended stream object time mapgeneral information (ESOB_TMAP_GI) shown in FIG. 55;

FIG. 68 exemplifies contents of the extended elementary stream time mapgeneral information (EES_TMAP_GI) shown in FIG. 55;

FIG. 69 exemplifies contents of the extended program chain information(EPGCI; or EORG_PGCI) shown in FIG. 46;

FIG. 70 exemplifies contents of the extended program chain generalinformation (EPGCI_GI) shown in FIG. 69;

FIG. 71 exemplifies contents of the extended program information (EPGI)shown in FIG. 69;

FIG. 72 exemplifies contents of the program resume marker information(PG_RSM_MRKI) shown in FIG. 71;

FIG. 73 exemplifies contents of the extended video time map informationtable (EVTMAPIT) shown in FIG. 46; and

FIG. 74 exemplifies contents of the extended stream time map informationtable (ESTMAPIT) shown in FIG. 46.

DETAILED DESCRIPTION OF THE INVENTION

Preferred embodiments of the present invention will be described indetail hereinafter with reference to the accompanying drawings.

FIG. 1 is a view for explaining the data structure according to anembodiment of the present invention. As disc-shaped informationrecording medium 100 (FIG. 1(a)), recordable optical discs such as aDVD-RAM, DVD-RW, DVD-R, and the like, and recordable magnetic discs suchas a hard disc and the like are available. The following explanationwill be given taking an optical disc such as a DVD-RAM or the like as anexample.

Disc 100 has lead-in area 110, volume/file structure information area111, data area 112, and lead-out area 113 from its inner periphery sidetoward the outer periphery side (FIG. 1(b)). Volume/file structureinformation area 111 stores a file system. The file system includesinformation indicating the recording locations of files. Recordedcontents are stored in data area 112 (FIG. 1(c)).

Data area 112 is divided into areas 120 that record general computerdata, and area 121 that records AV data. AV data recording area 121includes AV data management information area 130 that stores a file(VMG/ESMG file) used to manage AV data, VR object group recording area122 that records object data (VOBS) files (VRO files) complying with thevideo recording standard, and EStream object group recording area 131that records stream objects (ESOBS: Extend Stream Object Stream)compatible to digital broadcast (FIG. 1(d)). That is, in thisembodiment, stream objects of digital broadcast are recorded as EStreamobjects 132 (ESOBS) as files independent from VR objects (FIG. 1(e)).

Each EStream object 132 is made up of one or more data units (ESOBU:Extend Stream Object Unit) 134 each of which serves as an access unit todisc 100 (FIG. 1(f)). Each data unit (ESOBU) 134 is made up of one ormore pack groups (Pack_Group), each of which includes a group of aplurality of packs (FIG. 1(g)). In this embodiment, each pack group 140includes a group of eight packs. If one pack size is 2 kbytes, the sizeof each pack group 140 is 16 kbytes. This size is equal to the ECC blocksize in the video recording standard. If the ECC block size is 32kbytes, each pack group 140 can include 16 packs (corresponding to 32kbytes). If the ECC block size is 64 kbytes, each pack group 140 caninclude 32 packs (corresponding to 64 kbytes).

Each pack group 140 forms packet recording area (DVD-TS packet recordingarea) 160 in stream recording proposed by the present invention (FIG.1(h)). DVD-TS packet recording area 160 can be formed of pack groupheader 161, a plurality of (e.g., 85) MPEG-TS packets 162, and aplurality of (e.g., 84) pieces of packet arrival time differenceinformation (IAPAT: Incremental Packet Arrival Time) (FIG. 1(i)). Thecontents of pack group 140 will be described in detail later withreference to FIG. 14.

FIG. 2 is a view for explaining the relationship among a playbackmanagement information layer, object management information layer, andobject layer in the data structure according to the embodiment of thepresent invention. Management information (VMG/ESMG file) recorded on AVdata management information recording area 130 in FIG. 1 has playbackmanagement information layer 10 used to manage the playback sequences ofboth the recorded contents based on the video recording standard and thestream recording recorded contents based on the present invention.

That is, a group of one or more cells 13 each of which serves as aplayback unit of stream-recorded objects forms program 12, and a groupof one or more cells 13* each of which serves as a playback unit ofvideo-recorded objects forms program 12*. A sequence (playback sequence)of these programs 12 and 12* is managed by management information (PGCI)of program chain (PGC) 11.

Even when the user wants to start playback from the middle of eithercell 13 on the stream recording side or cell 13* on the video recordingside, he or she can designate the playback location using a playbacktime (PTS).

That is, when playback is to start from the middle of cell 13 on thestream recording side using the playback time (PTS), stream object ESOB132 in stream object layer 30 is designated via stream objectinformation ESOBI 21 in stream object management information layer 20,and stream object unit ESOBU 134 in stream object layer 30 is designatedvia stream object unit information ESOBUI 22 in stream object managementinformation layer 20. When ESOB 132 and its ESOBU 134 are designated,the playback start location is specified. (ESOBUI in this case may berestated as global information 22.)

This ESOBU 134 is formed of one or more pack groups 140. ESOBU 134corresponds to, e.g., 1 or 2 GOP data. If no GOP delimiter is found,ESOBU 134 is delimited in units corresponding to a data amount for amaximum of 1 sec as a playback time. In this way, overflow of eachinformation field is prevented. Each pack group 140 may be formed of 8packs (16384 bytes), and has pack group header 161 at its head position.Pack group header 161 is followed by a plurality of transport streampackets (TS_Packet) 162 and a plurality of pieces of packet arrival timedifference information (IAPAT) 163. These TS packets 162 store streamrecording recorded contents.

On the other hand, when playback is to start from the middle of cell 13*on the video recording side using the playback time (PTS), video objectVOB 36 in video object layer 35 is designated via video objectinformation VOBI 24 in video object (VOB) management information layer23, and video object unit VOBU 37 in video object layer 35 is designatedvia video object unit information VOBUI 25 in video object managementinformation layer 23. When VOB 36 and its VOBU 37 are designated, theplayback start location is specified. VOBU 37 may be formed of aplurality of packs 38, which store video recording recorded contents.

As will be described in detail later, when playback is to start from themiddle of cell 13 on the stream recording side, the playback startlocation can be designated using a time in units of the number of fieldsby ESOBU_PB_TM (FIG. 8). On the other hand, when the playback is tostart from the middle of cell 13* on the video recording side, theplayback start location can be designated by VOBU_PB_TM (not shown) intime map information (TMAPI) specified by the video recording standard.

The contents of FIG. 2 can be summarized as follows. That is, streamrecording management data (PCGI) can be recorded in a file common tovideo recording, and stream recording can be controlled common to videorecording. Also, stream recording and video recording can be linked forrespective cells, and the playback location in each of stream recordingand video recording can be designated by a playback time.

Irrespective of the recording method (stream or video recording), aftera given broadcast program (program) is recorded on disc 100, specialplayback requirements (e.g., the user wants to start playback (timesearch) from a desired time or to make fast-forwarding(FF)/fast-rewinding (FR) in a desired program) are often generated. Tomeet such requirements, special management information is required tomanage recorded data.

This management information will be described below with reference toFIGS. 3 to 13.

FIG. 3 is a view for explaining an example of the configuration of afield (RTR_VMGI) of one management information (RTR_VMG) recorded on AVdata management information recording area 130 shown in FIG. 1.

Note that stream recording in this embodiment will be abbreviated as ESR(Extended Stream Recording), and video recording will be abbreviated asVR. Then, management information of ESR data is saved in RTR_VMG 130,and is managed in the same way as VR data, as shown in FIG. 3.

RTR_VMG 130 includes video manager information (RTR_VMGI) 1310, streamfile information table (ESFIT: Extend Stream File Information Table)1320, (original) program chain information (ORG_PGCI) 1330, and playlist information (PL_SRPT: or user-defined program information table:UD_PGCIT) 1340.

Note that the play list and user-defined program chain havesubstantially equivalent meanings although they have different names,and are synonymous with a play list and user-defined program chain usedin the video recording standard. Hence, in the following description,play list related information (PL_SRP and the like) and user-definedprogram chain related information (UD_PGCIT_SRP and the like) areincluded as needed.

RTR_VMGI 1310 includes disc management identification information(VMG_ID/ESMG_ID) 1311, version information (VERN) 1312, EStream objectmanagement information start address (ESFIT_SA) 1313, program chaininformation start address (ORG_PGCI_SA) 1315, and play list informationstart address (UD_PGCIT_SA) 1316. ESR stream management information issaved in ESFIT 1320.

FIG. 4 is a view for explaining an example of the configuration of ESFIT1320 in FIG. 3. This ESFIT 1320 includes stream file information tableinformation (ESFITI) 1321, one or more pieces of ESOB stream information(ESOB_STI#1 to ESOB_STI#m) 1322, and stream file information (ESFI)1323. (Note that 1321 may be considered as general information.)

FIG. 5 is a view for explaining an example of the configuration ofESFITI 1321 and ESFI 1323 in FIG. 4. ESFITI 1321 includes information13211 indicating the number of ESOBs, information 13212 indicating thenumber of pieces of ESOB_STI, and information 13213 indicating the endaddress of the ESFIT. ESFI 1323 includes general information ESFI_GI13231, one or more pieces of stream object information (ESOBI#1 toESOBI#m) 13233, and one or more search pointers (ESOBI_SRP#1 toESOBI_SRP#m) 13232 for these (ESOBI#1 to ESOBI#m).

FIG. 6 is a view for explaining the configuration of each stream objectinformation (e.g., ESOBI#1) 13233 in FIG. 5. This ESOBI#1 13233 includesstream object general information (ESOB_GI) 13221, and one or morepieces of map group information (MAP_GroupI#1 to MAP_GroupI#n) 13222.

ESOB_GI 13221 includes PAT/PMT (Program Association Table/Program MapTable) 1322100 for all of one or more streams, recording start timeinformation 1322101, ESOB start PTS/ATS (Presentation Time Stamp/ArrivalTime Stamp; presentation time stamp/first TS packet arrival time)1322102, ESOB end PTS/ATS 1322103, file pointer (relative address)1322104 of the first ESOBU in that ESOB, received stream packet length(188 bytes for TS packets) 1322105, number (85 for TS packets) of streampackets 1322106 in a pack group, the number of map groups 1322107, andthe number of entries 1322108 of map group #1 to the number of entries1322109 of map group #n for one or more map groups.

Also, each map group information (e.g., MAP_GroupI#n) 13222 includes mapgroup general information (MAP_Group_GI) 132220, one or more map entries(MAP_ENT#1 to MAP_ENT#r) 132221, and one or more ESOBU entries(ESOBU_ENT#1 to ESOBU_ENT#q).

FIG. 7 is a view for explaining an example of the configuration ofMAP_Group_GI 132220 and each map entry (e.g., MAP_ENT#r) 132221 in FIG.6.

MAP_Group_GI 132220 includes the number of map entries (M_ENT_NUMs)1322201, the number of ESOBU entries (ESOBU_ENT_NUMs) 1322202, timeoffset information (TM_OFS) 1322203, address offset information(ADD_OFS) 1322204, ESOBU type information 1322205, and PMT_ID/program IDinformation 1322206.

Note that ESOBU type information 1322205 includes:

type information=“00” . . . video data available;

type information=“01” . . . video data not available, audio dataavailable;

type information=“10” . . . other.

MAP_ENT#r 132221 includes ESOBU entry number (ESOBU_ENTN) 1322221, timedifference (TM_DIFF) 1322222, and target ESOBU address (TargetESOBU_ADR) 1322223. This Target ESOBU_ADR 1322223 can be expressed bythe number of TS packets or the number of packs (the number of sectors)of a disc.

FIG. 8 is a view for explaining an example of the configuration ofESOBU_ENT#1 132222 shown in FIG. 6. ESOBU_ENT#1 132222 includesinformation 132231 indicating the number of packs or the number of TSpackets of 1st_Ref_PIC, ESOBU playback time (ESOBU_PB_TM: correspondingto the number of video fields) 132232, ESOBU size (ESOBU_SZ; which canbe expressed by the number of TS packets or the number of packs) 132233,and playback time (1st_Ref_PIC_PTM) 132234 of PCR_Pack number or1st_Ref_PIC.

Note that there are three types of ESOBU, i.e., a case wherein videodata is available, a case wherein no video data is available but audiodata is available, and a case of only other kinds of information. Thesetypes are respectively expressed by <1>, <2>, and <3>. That is, thereare three types of ESOBU entry information in accordance with theaforementioned types.

FIG. 9 is a view for explaining an example of the contents of ESOBUentry information 132222 shown in FIG. 8 depending on the availabilityof video and audio data.

<1> When video data is available, ESOBU entry information includes theend address information of the first reference picture (I picture or thelike) in an entry from the head of ESOBU, ESOBU playback time (thenumber of fields), ESOBU size, and pack number with the PCR, orreference picture playback time (the number of fields from the head ofESOBU). Note that the PCR is the closest one which is located before theposition of the reference picture.

More specifically, when video data is available:

ESOBU is delimited (a) at randomly accessible positions, (b) in unitscorresponding to an integer multiple of GOP, or (c) within a maximum of1 sec as a playback time.

The number of packs of 1st_Ref_PIC is that from the head of ESOBU to theend of the reference picture (Ref_PIC). When the number of packs is“0xffffffff”, it indicates that Ref_PIC is not present or found in thatSOBU. In this case, this SOBU cannot be used as an access point uponspecial playback.

The PCR_Pack number indicates the number of packs from the head of ESOBUclosest to 1st_Ref_PIC to a pack that stores the PCR. The first bit ofthe PCR_Pack number is used as a (flag (e.g., “0” indicates “+direction”; “1” indicates “− direction”). If no PCR is available, thePCR_Pack number is set to be “0xfff”, or the playback time of1st_Ref_PIC (1st_Ref_PIC_PTM) can be adopted instead.

<2> When video data is not available and audio data is available, ESOBUentry information includes the end address information of the firstaudio frame in an entry from the head of ESOBU, ESOBU playback time (thenumber of fields), ESOBU size, and pack number with the PCR.

More specifically, when video data is not available and audio data isavailable:

ESOBU is delimited at 1-sec intervals.

The number of packs of 1st_Ref_PIC is the number of last packs of theaudio frame at the head of ESOBU.

The PCR_Pack number indicates the number of packs from the head of SOBUclosest to an audio frame at the head of ESOBU to a pack that stores thePCR. The first bit of the PCR_Pack number is used as a (flag (e.g., “0”indicates “+ direction”; “1” indicates “− direction”). If no PCR isavailable, the PCR_Pack number is set to be “0xffff”.

<3> When only other kinds of information are available, since entryinformation cannot be formed, all data are padded with “FF”s.

More specifically, when neither video data nor audio data are available,and only other kinds of information (data broadcast information and thelike) are available:

ESOBU is delimited at 1-sec intervals.

The number of packs of 1st_Ref_PIC is fixed to “0xffffffff”.

The PCR_Pack number is fixed to “0xffffffff”.

FIG. 10 is a view for explaining an example of the configuration ofanother management information (stream data management informationRTR_ESMG) recorded on AV data management information recording area 130shown in FIG. 1. That is, stream data management information recordingarea 130 as a part of AV data management information recording area 130includes disc management information (ESMGI_MAT) 1310, stream objectmanagement information (ESFIT; global information) 1320, program chaininformation (ORG_PGCI) 1330, and play list information (UD_PGCIT) 1340.

Program chain information (PGCI) 1330 includes program chain generalinformation (PGC_GI) 1331, one or more pieces of program information(PGI#1 to PGI#p) 1332, and one or more pieces of cell information (CI#1to CI#q) 1333. This PGCI data structure has substantially the sameformat as that of the video recording standard, except for its contents(cell information CI) (this difference will be explained below withreference to FIG. 11).

FIG. 11 is a view for explaining an example of the contents ofrespective elements of the program chain information shown in FIG. 10.

Program chain general information 1331 includes the number of programs(PG_Ns) 13311, and the number of cells (CI_SRP_Ns) 13312 in the programchain.

Each program information 1332 includes program type (PG_TY) 13321, thenumber of cells (C_Ns) 13322 in the program, and program contentsinformation (primary text information PRM_TXTI, item text search pointernumber IT_TXT_SRPN, representative picture information REP_PICTI, andthe like) 13323.

Each cell information 133 includes cell type (C_TY) 13331, cell playbacktime 13332, corresponding ESOB number 13333, cell start PTS/ATS(presentation time stamp/ESOBU arrival time) 13334, cell end PTS/ATS13335, and map group number/PMT_ID 13345. Note that an embodiment inwhich cell playback time 13332 in cell information is omitted is alsoavailable.

Note that cell type 13331 includes:

C_TY=“0” . . . VR moving picture (M_VOB);

C_TY=“1” . . . VR still picture (S_VOB);

C_TY=“2” . . . streamer (ESOB).

FIG. 12 is a view for explaining an example of the configuration of thecontents of the play list information shown in FIG. 10.

The play list information (PL_SRPT or user-defined PGC information tableUD_PGCIT) includes play list general information (PL_SRPT₁ or UD_PGCITI)1341, one or more play lists (their search pointers PL_SRP#1 to PL_SRP#ror UD_PGCI_SRP#1 to UD_PGCI_SRP#r) 1342, and one or more pieces of cellinformation (CI#1 to CI#s) 1343.

FIG. 13 is a view for explaining an example of the configuration ofrespective elements of the play list information shown in FIG. 12.

Play list general information 1341 includes the number of play lists(PL_SRP_Ns) 13411, and the number of cells (C_Ns) 13412 in all the playlists. Each play list 1342 includes play list type (PL_TY) 13421, thenumber of cells (C_Ns) 13422 in the play list, and play list contentsinformation (play list creation time PL_CREATE_TM, primary textinformation PRM_TXTI, item text search pointer number IT_TXT_SRPN,representative picture information REP_PICTI, and the like) 13423. Eachcell information 1343 includes cell type (C_TY) 13341, cell playbacktime 13342, reference ESOB number (ESON) 13343, cell start PTS/ATS(presentation time stamp/ESOBU arrival time) 13344, cell end PTS/ATS13345, and map group number/PMT_ID 13345. Note that an embodiment inwhich cell playback time 13342 in cell information is omitted is alsoavailable.

Note that cell type 13341 includes:

C_TY=“0” . . . VR moving picture (M_VOB);

C_TY=“1” . . . VR still picture (S_VOB);

C_TY=“2” . . . streamer (ESOB).

In the embodiment of the present invention, PGC information is used asplayback information, and has the same format as that of videorecording. However, in the cell information shown in FIGS. 11 and 13,the ESOB type is added to the cell type. Furthermore, the ESOB number isdesignated, and two types of the playback start time and end time, i.e.,start PTS and ATS (or APAT) and end PTS and ATS are assumed. Moreover,the map group number or stream number is assumed.

In the embodiment of the present invention, the structure of the extendstream object set (ESOBS) is made up of one or more extend streamobjects (ESOB), each of which corresponds to, e.g., one program. EachESOB includes one or more ESOBUs (Extend Stream Object Units), each ofwhich corresponds to object data for 1 sec as a playback time or one ortwo GOP data

FIG. 14 is a view for explaining an example of the configuration of thestream object data unit (ESOBU) shown in FIG. 1 or 2.

One ESOBU includes one or more pack groups 140, each of which includes,e.g., 8 packs (1 pack=1 sector: 2048 bytes).

Each pack group 140 includes pack group header (152 bytes) 161, one ormore (85 in this case) MPEG-TS packets (188 bytes) 162, and one or more(84 in this case) IAPAT (Incremental Packet Arrival Time; 3 bytes) data163.

Pack group header 161 includes pack arrival time (ATS) 151, copygeneration management information (or copy control information CCI) 152,display control information (DCI) 153, manufacturer's information (MNI)154, presentation time information (PTS) 155, and PCR locationinformation (PCRI; Program Clock Reference Information) 156.

Each MPEG-TS packet 162 includes 4-byte header 170 and adaptation fieldand/or payload 180. Note that header 170 includes sync byte 171,transport error indicator 172, payload unit start indicator 173,transport priority 174, packet identifier (PID) 175, transport scramblecontrol 176, adaptation field control 177, and continuity index 178.

A TS stream (FIG. 14) as a common basic format in systems that broadcast(distribute) compressed moving picture data such as digital TV broadcastdata and broadcast data using a wired network such as the Internet orthe like is divided into a packet management data field (170) andpayload (180).

The payload includes data to be played back in a scrambled state.According to the digital broadcast standard ARIB, the PAT (ProgramAssociation Table), PMT (Program Map Table), and SI (ServiceInformation) are not scrambled. Also, various kinds of managementinformation can be generated using the PMT and SI (SDT: ServiceDescription Table, EIT: Event Information Table, BAT: BouquetAssociation Table).

Data to be played back includes MPEG video data, Dolby AC3 (audio data,MPEG audio data, data broadcast data, and the like. As informationrequired upon playback, a plurality of pieces of information (programinformation and the like) such as PAT, PMT, SI, and the like are usedalthough they are not directly related to data to be played back.

The PAT includes the PID (Packet Identification) of the PMT for eachprogram, and the PMT records the PIDs of video data and audio data.

In this way, a normal playback sequence of the STB (Set Top Box) is asfollows. That is, when the user determines a program from EPG(Electronic Program Guide) information, the PAT is loaded at thebeginning of the target program, and determines the PID of the PMT,which belongs to the desired program, on the basis of that data. Thetarget PMT is read out in accordance with that PIT, and the PIDs ofvideo and audio packets to be played back, which are contained in thePMT, are determined. Video and audio attributes are read out based onthe PMT and SI and are set in respective decoders. The video and audiodata are extracted and played back in accordance with their PIDs. Notethat the PAT, PMT, SI, and the like are transmitted at intervals ofseveral 100 ms since they are used during playback.

Upon recording on a disc medium such as a DVD-RAM or the like usingthese data, it is advantageous to directly record broadcast data asdigital data.

If a plurality of streams are to be recorded at the same time, thenumber of streams to be recorded may be stored in SOBI, PMT datacorresponding to respective streams may be saved, special playback mapinformation (map group information) may be stored for each stream, andthe numbers of streams to be played back (channel numbers or PID data ofPMT data) may be recorded in cell information.

FIG. 15 is a view for explaining an example of the configuration of packarrival time (ATS) 151 contained in the pack group header shown in FIG.14. For example, 6 bytes are assigned to ATS 151. The upper bytes of ATS151 represent PAT-base (e.g., a counter value of 90 kHz) and the lowerbyte represents PAT-extend (e.g., a counter value of 27 MHz).

Practical arrival time PAT is expressed by PAT_base/90000Hz+PAT_exten/27,000,000 Hz. In this manner, ATS 151 can be finelyexpressed for, e.g., respective video frames.

FIG. 16 is a view for explaining an example of the configuration of copygeneration management information (or copy control information CCI)contained in the pack group header shown in FIG. 14. In this case, 32bytes are assigned to CCI 152. As the contents, a reserve bit (1 bit) isassigned at the head of the information, and a set (3 bits) of digitalcopy control information (2 bits) and analog copy control information (1bit) is repetitively assigned 85 times.

Note that the digital copy control information indicates “copy never” ifit is “00”; “copy once” if it is “01”; and “copy free” if it is “11”.Also, the analog copy control information indicates “copy free” (noanalog protection system APS) if it is “0”; and “copy never” (with APS)if it is “1”. The copy control information value can be set based on avalue (see FIGS. 35 to 37) recorded in SI in a stream (contents).

FIG. 17 is a view for explaining an example of the configuration ofdisplay control information (DCI) 153 contained in the pack group headershown in FIG. 14. In this case, 32 bytes are assigned to DCI 153. As thecontents, a reserve bit (1 bit) is assigned at the head of theinformation, and a set (3 bits) of aspect information (1 bit),interlaced/progressive (I/P) information (1 bit), andstandard/high-definition (SD/HD) information (1 bit) is repetitivelyassigned 85 times.

Note that the aspect information indicates an aspect ratio 4:3 if it is“0”; and 16:9 if it is “1”. The I/P information indicates interlaceddisplay if it is “0”; and progressive display if it is “1”. The SD/HDinformation indicates standard image quality (image quality of standardNTSC or PAL class) if it is “0”; and high-definition image quality(image quality of high-definition or Hi-Vision class) if it is “1”. Theaspect information value can be set based on a value (see FIGS. 38 and39) recorded in SI in a stream (contents).

FIG. 18 is a view for explaining an example of the configuration ofincrement (IAPAT) 163 of the packet arrival time contained in the packgroup shown in FIG. 14 after the pack group header. In this case, forexample, 3 bytes are assigned to IAPAT 163. The upper 2 bytes of IAPAT163 express PAT-base (e.g., a counter value of 90 kHz) and the lower 1byte represents PAT-extend (e.g., a counter value of 27 MHz). SinceIAPAT 163 can be expressed by an increment (change) from ATS 151 inplace of an absolute time, the data size of IAPAT can be smaller thanthat of ATS.

Practical arrival time PAT in IAPAT 163 is expressed byATS+PAT_base/90000 Hz+PAT_exten/27,000,000 Hz. In this manner, IAPAT 163can be finely expressed for, e.g., respective video frames. As anotherembodiment, a difference from the arrival time of the immediatelypreceding TS packet may be used.

Note that “PAT” in “PAT-base and PAT-exten” shown in FIG. 15 or 18 meansnot “Program Association Table” but “Packet Arrival Time”.

FIG. 19 is a view for explaining an example of the configuration of PCRlocation information (PCR_Pack number or the like) contained in the packgroup header shown in FIG. 14. In this case, PCR (Program ClockReference) location information 156 is used as PCR information (PCRI).

This PCR location information 156 is expressed by, e.g., 2 bytes. These2 bytes can express a PCR pack number. This PCR pack number can beexpressed by the number of packs from the head of ESOBU closest to firstreference picture (i.e., first I-picture) 1st_Ref_PIC to a pack thatstores the PCR. The first bit of the PCR pack number is used as a (flag(e.g., “0” indicates “+ direction”; “1” indicates “− direction”). If noPCR is available, the PCR_Pack number is set to be “0xfff”.

FIG. 20 is a block diagram for explaining an example of the apparatuswhich records and plays back AV information (digital TV broadcastprogram or the like) on an information recording medium (optical disc,hard disc, or the like) using the data structure according to theembodiment of the present invention.

As shown in FIG. 20, this apparatus (digital video recorder/streamer)comprises MPU unit 80, key input unit 103, remote controller receiver103 b for receiving user operation information from remote controller103 a, display unit 104, decoder unit 59, encoder unit 79, system timecounter (STC) unit 102, data processor (D-PRO) unit 52, temporarystorage unit 53, disc drive unit 51 for recording/playing backinformation on/from recordable optical disc 100 (e.g., a DVD-RAM or thelike), hard disc drive (HDD) 100 a, video mixing (V-mixing) unit 66,frame memory unit 73, analog TV D/A converter 67, analog TV tuner unit82, terrestrial digital tuner unit 89, and STB (Set Top Box) unit 83connected to satellite antenna 83 a. Furthermore this apparatuscomprises digital I/F 74 (e.g., IEEE1394) to cope with digitalinputs/outputs as a streamer.

Note that STC unit 102 counts clocks on a 27-MHz basis in correspondencewith PAT_base shown in FIG. 15 or 18.

STB unit 83 decodes received digital broadcast data to generate an AVsignal (digital). STB unit 83 sends the AV signal to TV 68 via encoderunit 79, decoder unit 59, and D/A converter 67 in the streamer, thusdisplaying the contents of the received digital broadcast.Alternatively, STB unit 83 directly sends the decoded AV signal(digital) to V-mixing unit 66, and can send an analog AV signal from itto TV 68 via D/A converter 67.

The apparatus shown in FIG. 20 forms a recorder comprising both thevideo and stream recording functions. Hence, the apparatus comprisescomponents (IEEE1394 I/F and the like) which are not required in videorecording, and those (AV input A/D converter 84, audio encode unit 86,video encode unit 87, and the like) which are not required in streamrecording.

Encoder unit 79 includes A/D converter 84, video encode unit 87, inputselector 85 to video encode unit 87, audio encode unit 86, a sub-pictureencode unit (as needed although not shown), format unit 90, and buffermemory unit 91.

Decode unit 59 comprises demultiplexer 60 which incorporates memory 60a, video decode unit 61 which incorporates memory 61 a and reduced-scalepicture (thumbnail or the like) generator 62, sub-picture (SP) decodeunit 63, audio decode unit 64 which incorporates memory 64 a, TS packettransfer unit 101, video processor (V-PRO) unit 65, and audio D/Aconverter 70. An analog output (monaural, stereo, or AAC 5.1CH surround)from this D/A converter 70 is input to an AV amplifier or the like (notshown) to drive a required number of loudspeakers 72.

In order to display contents, whose recording is in progress, on TV 68,stream data to be recorded is sent to decoder unit 59 simultaneouslywith D-PRO unit 52, and can be played back. In this case, MPU unit 80makes setups upon playback in decoder unit 59, which then automaticallyexecute a playback process.

D-PRO unit 52 forms ECC groups by combining, e.g., every 16 packs,appends ECC data to each group, and sends them to disc drive unit 51.When disc drive unit 51 is not ready to record on disc 100, D-PRO unit52 transfers the ECC groups to temporary storage unit 53 and waits untildisc drive unit 51 is ready to record. When disc drive unit 51 is ready,D-PRO unit 52 starts recording. Temporary storage unit 53 may be assuredby using a given area of HDD 100 a.

Note that MPU unit 80 can make read/write access to D-PRO unit 52 via adedicated microcomputer bus.

The apparatus shown in FIG. 20 assumes optical disc 100 such asDVD-RAM/-RW/-R/Blue media (recordable media using blue laser) and thelike as primary recording media, and hard disc drive (HDD) 100 a (and/ora large-capacity memory card (not shown) or the like) as its auxiliarystorage device.

These plurality of types of media can be used as follows. That is,stream recording is done on HDD 100 a using the data structure (format)shown in FIGS. 1 to 19. Of stream recording contents which are recordedon HDD 100 a, programs that the user wants to preserve directly undergostream recording (direct copy or digital dubbing) on disc 100 (ifcopying is not inhibited by copy control information CCI). In thismanner, only desired programs having quality equivalent to originaldigital broadcast data can be recorded together on disc 100.Furthermore, since the stream recording contents copied onto disc 100exploit the data structure of the present invention, they allow easyspecial playback processes (to be described later with reference to FIG.44) such as time search and the like, although these contents arerecorded by stream recording.

A practical example of a digital recorder having the aforementionedfeatures (a streamer/video recorder using a combination of aDVD-RAM/-RW/-R/Blue media and HDD) is the apparatus shown in FIG. 20.The digital recorder shown in FIG. 20 is configured to roughly include atuner unit (82, 83, 89), disc unit (100, 100 a), encoder unit 79,decoder unit 59, and a controller (80).

Satellite digital TV broadcast data is delivered from a broadcaststation via a communication satellite. The delivered digital data isreceived and played back by STB unit 83. This STB 83 expands and playsback scrambled data on the basis of a key code distributed from thebroadcast station. At this time, scramble from the broadcast station isdescrambled. Data is scrambled to prevent users who are not subscribersof the broadcast station from illicitly receiving broadcast programs.

In STB unit 83, the broadcast digital data is received by a tuner system(not shown). When the received data is directly played back, it isdescrambled by a digital expansion unit and is decoded by an MPEGdecoder unit. Then, the decoded received data is converted into a TVsignal by a video encoder unit, and that TV signal is externally outputvia D/A converter 67. In this manner, the digital broadcast programreceived by STB unit 83 can be displayed on analog TV 68.

Terrestrial digital broadcast data is received and processed insubstantially the same manner as satellite broadcast data except that itdoes not go through any communication satellite (and is not scrambled ifit is a free broadcast program). That is, terrestrial digital broadcastdata is received by terrestrial digital tuner unit 89, and the decodedTV signal is externally output via D/A converter 67 when it is directlyplayed back. In this way, a digital broadcast program received byterrestrial digital tuner unit 89 can be displayed on analog TV 68.

Terrestrial analog broadcast data is received by terrestrial tuner unit82, and the received analog TV signal is externally output when it isdirectly played back. In this way, an analog broadcast program receivedby terrestrial tuner unit 82 can be displayed on analog TV 68.

An analog video signal input from external AV input 81 can be directlyoutput to TV 68. Also, after the analog video signal is temporarilyA/D-converted into a digital signal by A/D converter 84, and thatdigital signal is then re-converted into an analog video signal by D/Aconverter 67, that analog video signal may be output to the external TV68 side. In this way, even when an analog VCR playback signal thatincludes many jitter components is input from external AV input 81, ananalog video signal free from any jitter components (that has undergonedigital time-base correction) can be output to the TV 68 side.

A digital video signal input from digital I/F (IEEE1394 interface) 74 isoutput to the external TV 68 side via D/A converter 67. In this way, adigital video signal input to digital I/F 74 can be displayed on TV 68.

A bitstream (MPEG-TS) input from satellite digital broadcast,terrestrial digital broadcast, or digital I/F 74 can undergo streamrecording in stream object group recording area 131 (FIG. 1(d)) of disc100 (and/or HDD 10 a) as stream object 132 in FIG. 1(e).

An analog video signal from terrestrial analog broadcast or AV input 81can undergo video recording on VR object group recording area 122 (FIG.1(d)) of disc 100 (and/or HDD 10 a).

Note that the apparatus may be configured to temporarily A/D-convert ananalog video signal from terrestrial analog broadcast or AV input 81into a digital signal, and to make stream recording of the digitalsignal in place of video recording. Conversely, the apparatus may beconfigured to make video recording of a bitstream (MPEG-TS) input fromsatellite digital broadcast, terrestrial digital broadcast, or digitalI/F 74 (after it undergoes required format conversion) in place ofstream recording.

Recording/playback control of stream recording or video recording isdone by firmware (control programs and the like corresponding tooperations shown in FIGS. 24 to 44 to be described later) of main MPUunit 80. MPU unit 80 has management data generation unit 80B for streamrecording and video recording, generates various kinds of managementdata (FIGS. 2 to 19 and the like) using work RAM 80A as a work area, andrecords the generated management information on AV data managementinformation recording area 130 in FIG. 1(d) as needed. MPU unit 80 playsback management information recorded on AV data management informationrecording area 130, and executes various kinds of control (FIGS. 24 to44) on the basis of the played back management information.

The features of medium 100 (10 a) used in the apparatus of FIG. 20 willbe briefly summarized below. That is, this medium has management area130 and data area 131. Data is separately recorded on the data area as aplurality of object data (ESOB), and each object data is made up of agroup of data units (ESOBU). One data unit (ESOBU) includes pack groupseach of which is formed by converting a MPEG-TS compatible digitalbroadcast signal into TS packets and packing a plurality of packets (seeFIGS. 1 and 14). On the other hand, management area 130 has PGCinformation (PCGI) as information used to manage the playback sequence.This PGC information contains cell information (CI) (see FIGS. 10 to13). Furthermore, management area 130 includes information used tomanage object data (ESOB) (see FIGS. 4 to 9).

The apparatus shown in FIG. 20 can make stream recording on medium 100(10 a) with the above data structure in addition to video recording. Inthis case, in order to extract program map table PMT and serviceinformation SI from a TS packet stream, MPU unit 80 has a serviceinformation extraction unit (not shown; firmware that forms managementdata management unit 80B). Also, MPU unit 80 has an attributeinformation generation unit (not shown; firmware that forms managementdata management unit 80B) that generates attribute information (PCR_Packnumber and the like in FIG. 8) on the basis of information extracted bythe service information extraction unit.

FIG. 21 shows an example of management information stored in AV datamanagement information recording area 130 shown in FIG. 1, and is a viewfor explaining the data structure as a combination of video recordingmanagement information VMG and stream recording management informationESMG according to the embodiment of the present invention. FIG. 21 showsan embedding example of information (ESFIT) used to manage MPEG-TS (oneof AV data) of recorded digital TV broadcast data of managementinformation stored in AV data management information recording area 130shown in FIG. 1. In FIG. 21, stream file information table (ESFIT) 1320that has been explained using FIGS. 4 and 5 is allocated after movie AVfile information table (M_AVFIT) 1370. After ESFIT, original programchain information (ORG_PGCI) 1330, user-defined PGC information table(UD_PGCIT) 1340, text data manager (TXTDT_MG) 1350, manufacturer'sinformation table (MNFIT) 1360 are allocated as in video recordingmanagement information VMG. Upon adopting such data structure ofmanagement information (similar to the video recording standard), itbecomes easier to effectively utilize existing control softwareresources that have been developed for recorders based on the existingvideo recording standard (by partially modifying them).

FIG. 22 is a view for explaining an example of the configuration of thecontents of stream information (one of ESOBI_STI#1 to ESOBI_STI#m)included in management information (ESFIT) 1322 shown in FIG. 21. ThisESOBI_STI includes, in turn from lower relative byte positions, videoattribute V_ATR, the number AST_Ns of audio stream, the number SP_Ns ofsub-picture streams, attribute A_ATR0 of audio stream #0, attributeA_ATR1 of audio stream #1, and pallet data SP_PLT of sub-picture data.

FIG. 23 is a view for explaining an example of the configuration of thecontents of video attribute information (V_ATR) included in the streaminformation shown in FIG. 22. This V_ATR includes information (MPEG1,MPEG2, or the like) indicating a video compression mode, information(NTSC, PAL, or the like, or SD, HD, or the like) indicating a TV mode,information indicating an aspect ratio, information indicating a videoresolution, and interlaced/progressive identification information I/P.

If the information indicating an aspect ratio is “00b”, it indicates anaspect ratio=4:3; if the information is “01b”, it indicates an aspectratio=16:9. If identification information I/P is “00”, it indicatesprogressive display; if the information is “01”, it indicates interlaceddisplay.

If the information indicating a video resolution is “000”, it indicateshorizontal*vertical resolutions=720*480; if the information is “001”, itindicates horizontal*vertical resolutions=704*480; if the information is“010”, it indicates horizontal*vertical resolutions=352*480; if theinformation is “011”, it indicates horizontal*verticalresolutions=352*240; if the information is “100”, it indicateshorizontal*vertical resolutions=544*480; if the information is “101”, itindicates horizontal*vertical resolutions=480*480; and if theinformation is “110”, it indicates horizontal*verticalresolutions=1920*1080. Note that 720*480 progressive display or1920*1080 interlaced or progressive display corresponds to the HDresolution of Hi-vision or equivalent. Other resolutions correspond tothe SD resolutions.

FIG. 24 is a flow chart (overall operation process flow) for explainingan example of the overall operation of the apparatus shown in FIG. 20.For example, when the power switch of the apparatus in FIG. 20 is turnedon, MPU unit 80 makes initial setups (upon factory shipment or afteruser's setups (step ST10). MPU unit 80 also makes display setups (stepST12) and waits for a user's operation. If the user has made a key inputfrom key input unit 103 or remote controller 103 a (step ST14), MPU unit80 interprets the contents of that key input (step ST16). The followingfour data processes are executed as needed in accordance with this inputkey interpretation result.

That is, if the key input is, for example, a key operation made to settimer program recording, a program setting process starts (step ST20).If the key input is a key operation made to start recording, a recordingprocess starts (step ST22). If the key input is a key operation made tostart playback, a playback process starts (step ST24). If the key inputis a key input made to output digital data to the STB, a digital outputprocess starts (step ST26). The processes in steps ST20 to ST26 areparallel executed as needed for respective tasks. For example, theprocess for outputting digital data to the STB (ST26) is parallelexecuted during the playback process (ST24). Or a new program settingprocess (ST20) can be parallel executed during the recording process(ST22) which is not timer program recording. Or by utilizing the featureof disc recording that allows high-speed access, the playback process(ST24) and digital output process (ST26) can be parallel executed duringthe recording process (ST22).

FIG. 25 is a flow chart (interrupt process flow) for explaining anexample of an interrupt process in the operation of the apparatus shownin FIG. 20. In the interrupt process in the control operation of MPUunit 80, an interrupt factor is checked (step ST30). If the interruptfactor indicates that an interrupt is generated due to “completion oftransfer for one pack to D-PRO unit 52”, the number of video recordingpacks is incremented by 1 (step ST301). If the interrupt factorindicates that an interrupt is generated due to “fetching ofsegmentation information from formatter unit 90”, a fetch interrupt flag(not shown) of segmentation information 1 is set (step ST302).

FIGS. 26 and 27 are flow charts (recording flow) for explaining anexample of the recording operation (ST22 in FIG. 24) of the apparatusshown in FIG. 20.

<01> Upon reception of a recording command from the key input unit, MPUunit 80 loads management data from disc drive unit 51 (step ST100) anddetermines an area to be read. At this time, MPU unit 80 checks the filesystem to determine whether or not recording can be proceeded (if arecordable space remains on disc 100 or HDD 100 a). If recording cannotbe proceeded (NO in step ST102), a message that advises accordingly isdisplayed for the user (step ST104), thus aborting the recordingprocess.

If recording can be proceeded (YES in step ST102), MPU unit 80 checks ifrecording to be made is stream recording of a digital broadcast signalor video recording of an analog broadcast signal (or video recording ofan analog signal obtained by D/A-converting a digital broadcast signal).If recording to be made is not stream recording of a digital broadcastsignal (NO in step ST106), a recording process based on the videorecording standard starts. If recording to be made is stream recordingof a digital broadcast signal (YES in step ST106), a recording startposition is determined based on the management data loaded in stepST100.

<02> The contents of the management area are set to write data in thedetermined area, and the write start address of video data is set indisc drive unit 51, thus preparing for data recording (step ST110).

<03> As part of initial setups for recording, the time of STC unit 102is reset (step ST112). Note that STC unit 102 is a system timer, andrecording/playback is done (for respective frames) with reference to thecount value of this timer.

<04> The PAT (included in an MPEG-TS stream from STB unit 83) of aprogram to be recorded is loaded to determine the PID required to fetchthe PMT of the target program. Then, the target PMT is loaded todetermine the PIDs of data (video, audio) to be decoded (to berecorded). At this time, the PAT and PMT are saved in work RAM 80A ofMPU unit 80, and are written in the management information (step ST116).VMG file data is written in the file system, and required information(FIG. 3) is written in VMGI.

<05> As part of initial setups for recording, recording setups ofrespective units are made (step ST112). At this time, a segmentationsetup of data and reception setup of TS packets are made in formatterunit 90. Also, the PID of data to be recorded is set to record only atarget video stream. Also, buffer memory unit 91 is set to start holdingof TS packets.

As part of recording start setups, a buffer data fetch start processfrom buffer memory unit 91 is set in formatter unit 90 (step ST114).Then, formatter unit 90 starts a buffer fetch process (to be describedlater with reference to FIG. 29).

<06> STI is generated based on the PMT (step ST120 in FIG. 27; detailsof this step will be described later using FIG. 28). Next, a storageprocess in buffer memory unit 91 starts (step ST130).

<07> If data stored in buffer memory unit 91 reaches a predeterminedsize (for one continuous data area CDA) (YES in step ST140), apredetermined ECC process (which generates an ECC block for 8 sectors/16kbytes or for 32 sectors/64 kbytes) is done via D-PRO unit 52, thusrecording the data on the disc (step ST142).

<08> During recording, segmentation information is saved in work RAM 80Aof MPU unit 80 (step ST146) periodically (before buffer RAM 91 offormatter unit 90 becomes full of data; YES in step ST144). Thesegmentation information to be saved is that of ESOBU data, i.e., thestart address or pack length of each ESOBU, the end address of I-picturedata, the ESOBU arrival time (ATS), or the like may be saved.

<09> The remaining space of disc 100 (or 100 a) during recording ischecked. If the remaining space becomes equal to or smaller than apredetermined value (e.g., 150 Mbytes), a small remaining space processmay be executed (not shown). As the small remaining space process, aprocess for erasing, if erasable unerased data (temporarily erased datathrown into a trash box file) remain on the disc, these data to increasethe remaining space is known. Alternatively, as the small remainingspace process, a process for increasing a recordable duration bylowering the recording rate (or by switching MPEG2 recording to MPEG1recording) if the physical remaining space remains the same is alsoknown. Also, when dummy packs used in after recording are recorded ondisc 100, a process for aborting recording of these dummy packs may beexecuted as part of the small remaining space process. Alternatively, aprocess for continuing relay recording on an unrecorded data of HDD 100a when the remaining space of disc 100 becomes small may be executed aspart of the small remaining space process.

<10> It is checked if recording is to end (if the user has pressed arecording end key or if no recordable space remains). If recording is toend (YES in step ST148), remaining segmentation information is fetchedfrom formatter unit 90, and is added to work RAM 91. These data arerecorded in management data (VMGI), and remaining information isrecorded in the file system (step ST150).

<11> If recording is not to end (NO in step ST148), the flow returns tostep ST140 to continue the data fetch process (step ST130) and writeprocess (step ST142).

FIG. 28 is a flow chart (STI setting process flow) for explaining anexample of the contents of the stream information generation process(ST120) shown in FIG. 27. In stream recording that records an MPEG-TSstream, a stream to be recorded contains the PMT, which describes astream type (to be described later with reference to FIG. 34).

In the stream information generation process (ST120), the stream type inthe PMT (FIG. 34) is checked (steps ST1200 and ST1202). If the streamtype is “0x01”, an MPEG1 video STI setting process is executed (stepST1204); if the stream type is “0x02”, an MPEG2 video STI settingprocess is executed (step ST1206); if the stream type is “0x03”, anMPEG1 audio STI setting process is executed (step ST1208); or if thestream type is “0x04”, an MPEG2 audio STI setting process is executed(step ST1210). Inner data are checked for these stream types, andvarious kinds of attribute information are set. Upon completion ofgeneration (setting process) of STI for all streams (NO in step ST1212),the control exits the process in FIG. 28 and advances to step ST130 inFIG. 27.

In the flow of signals upon recording shown in FIGS. 26 to 28, TS packetdata received by STB unit 83 (or terrestrial digital tuner 82) areconverted into pack groups by formatter unit 90, and these pack groupsare saved in buffer RAM 91. When TS packet data as pack groups storedthe buffer RAM 91 reach a predetermined size (for one or an integermultiple of CDA size), they are recorded on disc 100. At this time, uponreception of TS packets, a group is formed every 85 packets, and a packgroup header is generated, as will be described below with reference toFIG. 29.

FIG. 29 is a flow chart (buffer fetch process flow) for explaining anexample of the contents of the buffer fetch process (ST130) shown inFIG. 27.

<01> A TS packet is received (step ST1300).

<02> If the fetched TS packet includes a PCR (YES in step ST1302), STCunit 102 is corrected (step ST1304).

<03> If the packet of interest corresponds to the head of a pack group(YES in step ST1306), its arrival time is fetched from the STC and issaved as ATS data (step ST1308). If the packet of interest does notcorrespond to the head of a pack group (NO in step ST1306), thedifference between the value of the ATS of the head packet and itsarrival time is allocated as IAPAT data before that TS packet (after theprevious TS packet) (step ST1310).

<04> It is checked if the PMT that has been fetched initially andbelongs to the current stream includes copy information. If the PMTincludes copy information (YES in step ST1312), copy control informationCCI (FIG. 16) is formed based on that information (FIGS. 36 and 37) andis saved in the pack group header (step ST1313) so as to write allpieces of information in the pack group header.

<05> If the PMT does not include any copy information (NO in stepST1312), and if the received TS packet does not include any copydescriptor (NO in step ST1314), copy information is formed based on thesame information as that of the previous pack (step ST1315). If thereceived TS packet includes a copy descriptor (YES in step ST1314), copycontrol information CCI (FIG. 16) is formed based on that informationand is saved in the pack group header (step ST1316).

<06> It is checked if the TS packet includes a component descriptor(FIG. 39). If the TS packet does not include any component descriptor(NO in step ST1318), the same information as that of the previous packis saved in the pack group header (step ST1319). If the TS packetincludes a component descriptor (YES in step ST1318), resolutioninformation (FIG. 17) is formed based on the included information (FIG.39), and is saved in the pack group header (step ST1320).

<07> It is determined whether or not a pack group is formed (morespecifically, whether or not 85 TS packets are grouped). If a pack groupis not formed yet (NO in step ST1322), the control returns to the headof buffer fetch process ST130; otherwise (YES in step ST1322), groupdata is temporarily saved in buffer RAM 91 (step ST1323).

If the head of a picture is included in a group, the PTS is saved withreference to the contents of the TS packet. If the TS packet contains novideo data but audio data alone, CCI is formed in accordance with audiocopy information. Furthermore, the availability of each information isdetected and is saved in work RAM 80A. Upon completion of recording, theinformation saved in work RAM 80A is recorded on management informationrecording area 130 as management information (ST150 in FIG. 27).

Upon playback, demultiplexer 60 interprets pack data read out from disc100 (or HDD 10 a) and sends a pack that includes TS packets to TS packettransfer unit 101. After that, the readout pack data are sent torespective decoders (61, 63, 64) and undergo corresponding playbackprocesses (video playback, sub-picture playback, audio playback).

Upon transferring TS packets to STB unit 83 (or to an external digitalTV or the like via IEEE1394 I/F 74), TS packet transfer unit 101transfers data of only TS packets at the same time intervals as theyarrived.

FIGS. 30 and 31 are flow charts (overall playback operation flow) forexplaining an example of the playback operation (ST24 in FIG. 24) of theapparatus shown in FIG. 20.

<01> A disc check process is made (step ST200) to check if the disc is arewritable disc (R, RW, RAM). If the disc is not a rewritable disc (NOin step ST200), a message that advises accordingly is returned (stepST202), thus ending the process.

<02> If the disc is a rewritable disc (YES in step ST200), the filesystem of the disc is read out to check if data has already beenrecorded (step ST204). If no data is recorded (NO in step ST204), amessage “no data is recorded” is displayed (step ST206), thus ending theprocess.

<03> If data has already been recorded (YES in step ST204), managementinformation (VMG file) 130 is loaded (step ST208) to determine programsand cells to be played back (by prompting the user to select them), andalso to determine the playback start file pointer (logical address)(step ST210). If a playback process in the recorded order is selected,playback is made according to ORG_PGCI (e.g., 1330 in FIG. 10). If aplayback process for respective programs is to be made (in the sequenceof user's choice), playback is made according to UD_PGCI (or play list1342 in FIG. 12) with a number corresponding to the program to be playedback.

<04> A process upon starting playback is executed (step ST212).

<05> Initial setups of respective decoders are made (step ST214).

<06> A cell playback process (to be described later with reference toFIGS. 32 and 33) is executed (step ST220). It is checked if playback isto end (step ST230). If playback is to end (YES in step ST230), an errorcheck process is executed (step ST240). If any error is found (YES instep ST240), a message that advises accordingly is displayed (stepST242), and a playback end process is executed (step ST244). If no erroris found (NO in step ST240), a playback end process is executed (stepST246), thus ending this operation.

<07> If playback is not to end (NO in step ST230), the next cell isdetermined based on PGCI (step ST232) and it is checked if setups ofdecoders (61, 64, and the like) are changed (step ST234). If the setupsare changed (YES in step ST234), change attributes are set in thedecoders so as to change decoder setups in response to the next sequenceend code (step ST236). After that, it is checked connection fromplayback of the previous cell to that of the next cell is seamless. Ifconnection is not seamless (NO in step ST238), MPEG decoders (61 and thelike) are set in a free run mode and a seamless connection flag is set(step ST239). The flow then returns to step ST220. If connection isseamless (YES in step ST238), the flow returns to step ST220.

<08> During the cell playback process (step ST220), it is checked ifplayback is to end (step ST230). If playback is not to end, the processin step ST220 is continued.

FIGS. 32 and 33 are flow charts (process flow upon cell playback) forexplaining an example of the process upon cell playback in the apparatusshown in FIG. 20. The cell playback process is executed as follows.

<01> A start file pointer (logical block address) and end address filepointer (logical block address) of a cell are determined on the basis ofprogram chain information PGCI and map information MAPI. A start FP(file pointer) of the cell is substituted in a read FP (file pointer),and a value obtained by subtracting the start file pointer from the endfile pointer is set in a remaining cell length (step ST2200).

<02> In decoder unit 59, a setup is made to execute a decode process. Atthis time, the PID of a TS packet to be played back is set to determinea target to be decoded. Note that the PID to be set is loaded from thePMT in ESOBI. In case of ESOB data for a plurality of streams, the PIDis determined using a program number in cell information.

<03> A read process during playback is executed to determine the readaddress and read size based on the start file pointer (step ST2202).

<04> The read size to be read out is compared with the remaining celllength. If the remaining cell length is larger than the read size (YESin step ST2204), a value obtained by subtracting the read size to beread out from the remaining cell length is set as the remaining celllength (step ST2206). If the remaining cell length is smaller than theread size (NO in step ST2204), the read size is set to be the remainingcell length, and the remaining cell length is set to be zero (stepST2208).

<05> The read length is set to be a read unit length, and the readaddress, read length, and read command are set in disc drive unit 51(step ST2210). After that, transfer of readout data from disc drive unit51 to D-PRO unit 52 starts (step ST2212).

<06> The control waits until readout data for one ESOBU are stored (in abuffer RAM (not shown) in D-PRO unit 52) (a loop formed if NO in stepST2214). If data for one ESOBU are stored (YES in step ST2214), the flowadvances to step ST2216.

<07> In decoder unit 59, readout pack group data is received bydemultiplexer 60 (step ST2216) and is demultiplexed into packets. Inaccordance with the stream ID and sub-stream ID, video packet data (MPEGvideo data) are transferred to video decode unit 61, audio packet dataare transferred to audio decode unit 64, and sub-picture packet data aretransferred to SP decode unit 63. TS transfer unit 101 converts readoutpack group data into an elemental stream, and sends it to respectivedecoders (61, 64) via an internal bus, thus executing decode processes.

If the resolution of the video signal is changed (e.g., an SD signal isswitched to an HD signal during playback) during the transfer process(YES in step ST2218), the control line of a D terminal arranged betweenD/A converter 67 and external TV 68 is changed (e.g., from D1 mode to D3mode) (step ST2220).

If the seamless connection flag is set (YES in step ST2222), read filepointer+read length is set in the read file pointer, MPEG decoder 61 isset in a normal mode (to read and set SCR), and the seamless connectionflag is set (step ST2224).

<08> During playback, the contents of STC 102 are displayed on displayunit 104 as a playback time. If STB unit 83 can display a playback timebased on the PTS in video data, that time can be used.

<09> It is checked if transfer is complete. If transfer does not start(NO in step ST2226), the flow returns to step ST2214.

<10> After the processes in steps ST2214 to ST2222, the sum of the readFP and the read length set in step ST2210 is substituted in the read FP(step ST2224).

<11> It is checked if transfer is complete. If transfer is complete (YESin step ST2226), the remaining cell length is checked. If the remainingcell length is not “00” (NO in step ST2228), the flow returns to stepST2202; otherwise, (YES in step ST2228), this process ends.

<12> If transfer is not complete yet (NO in step ST2226), it is checkedif a key input is detected (step ST2230). If a special playback processis to be made (YES in step ST2232 or YES in step ST2236), its directionis set, read file pointer FP is calculated using map information MAPI,and a read process upon special playback (steps ST2234 and ST2238) isexecuted, thus ending this process. If no special playback process is tobe made (NO in step ST2232, NO in step ST2236), the flow returns to stepST2214.

Target file pointer FT of special playback is calculated based on mapinformation MAPI to skip a predetermined period of time. At this time, amethod of calculating FP by skipping a predetermined number of ESOBUdata in place of the predetermined period of time is available. If theend of a given cell is reached, the next cell information is read outbased on program chain information PGCI, an ESOB number and MAPI thatthe next cell uses are selected, and the read FP is calculatedsimilarly. If no cell to be played back remains, the process ends atthat time.

FIG. 34 is a view for explaining an example of the data structure ofprogram map table PMT which can be used by the apparatus of FIG. 20. Inthis PMT, 8-bit stream type 3421 allows to identify various streams. Forexample, if the stream type is “0x01”, it indicates an MPEG1 videostream; if the stream type is “0x02”, it indicates an MPEG2 video stream(in case of Hi-Vision); if the stream type is “0x03”, it indicates anMPEG1 audio stream; and if the stream type is “0x04”, it indicates anMPEG2 audio stream (in case of AAC multi-channel audio).

FIG. 35 is a view showing an example of the contents of a digital copycontrol descriptor that can be used in the PMT in FIG. 34 and the like(service description table SDT, event information table EIT, and thelike).

In this descriptor, a “descriptor tag” field is set to be, e.g., “0xC1”,and a “descriptor length” field indicates the descriptor length. A“digital recording control” field describes “copy generation controldata”. A “maximum bit rate flag” field describes “whether or not themaximum transfer rate of the service of interest is to be described”. Ifthe maximum transfer rate is not described, the flag is set to be, e.g.,“0”; otherwise, the flag is set to be, e.g., “1”. When “0” is describedin a “component control flag” field, for example, the overall program isspecified (in case of PMT). If “1” is described in this field, anotherstate is described. A “copy control type” field describes “copygeneration control data” (see FIGS. 36 and 37). An “APS control data”field describes “analog output control data” (see FIG. 36). A “maximumbit rate” field describes a “maximum transfer rate” (when the maximumbit rate flag is “1”).

FIG. 36 is a view for explaining an application example of digital copycontrol to video data. Copy control of video data is roughly categorizedinto three types, i.e., “unlimited copy permission (copy free)”, “copyinhibition (copy never or copy no more)”, and “copy permission of onlyone generation (copy once)”.

In case of “unlimited copy permission”, analog copy control is set to be“unlimited copy permission”, digital recording control is set to be,e.g., “01”, control type is set to be, e.g., “00”, and APS control datais set to be, e.g., “Don't care (ignore)”.

In case of “copy inhibition”, (1) analog copy control is set to be “copyinhibition (digital copy is inhibited, but analog copy is not inhibitedsince no copy protection pulses of the Macrovision (system areinserted)”, digital recording control is set to be, e.g., “01”, controltype is set to be, e.g., “11”, and APS control data is set to be, e.g.,“00”.

In case of “copy inhibition”, (2) analog copy control is set to be “copyinhibition (both analog copy and digital copy are inhibited)”, digitalrecording control is set to be, e.g., “01”, control type is set to be,e.g., “11”, and APS control data is set to be, e.g., “other than 00”.

In case of “copy permission of only one generation”, (3) analog copycontrol is set to be “copy permission of only one generation (analogcopy is permitted since no copy protection pulses are inserted)”,digital recording control is set to be, e.g., “01”, control type is setto be, e.g., “10”, and APS control data is set to be, e.g., “00”.

In case of “copy permission of only one generation”, (4) analog copycontrol is set to be “copy permission of only one generation (bothanalog copy and digital copy of the next and subsequent generation areinhibited)”, digital recording control is set to be, e.g., “01”, controltype is set to be, e.g., “10”, and APS control data is set to be, e.g.,“00”.

FIG. 37 is a view for explaining an application example of digital copycontrol to audio data. Copy control of audio data is also roughlycategorized into three types, i.e., “unlimited copy permission (copyfree)”, “copy inhibition (copy never or copy no more)”, and “copypermission of only one generation (copy once)”.

In case of “unlimited copy permission”, digital recording control is setto be, e.g., “01/11”, and control type is set to be, e.g., “00”.

In case of “copy permission of only one generation”, digital recordingcontrol is set to be, e.g., “01/11”, and control type is set to be,e.g., “10”.

In case of “copy inhibition”, digital recording control is set to be,e.g., “01/11”, and control type is set to be, e.g., “11”.

FIG. 38 is a view showing an example of the contents of a componentdescriptor that can be used by the PMT shown in FIG. 34 and the like(event information table EIT and the like).

In this descriptor, a “descriptor tag” field is set to be, e.g., “0x50”,and a “descriptor length” field indicates the descriptor length. A“stream contents” field describes, e.g., “0x01” indicating video. A“component type” field describes, e.g., a “type of component”. A“component tag” field describes, e.g., a “common tag in a program”. An“ISO_639 language code” field describes, e.g., “jpn” indicating aJapanese language code. A “Text_Char” field can describe characterstrings such as “video”, “audio”, and the like.

FIG. 39 is a view for explaining an example of the contents of componenttypes shown in FIG. 38. When the component type is “0x01”, it indicates,e.g., that “video 480 interlaced (or 525 interlaced) and aspectratio=4:3”. When the component type is “0x03”, it indicates, e.g., that“video=480 interlaced (or 525 interlaced), aspect ratio=16:9, and panvector=none”. When the component type is “0x04”, it indicates, e.g.,that “video=480 interlaced (or 525 interlaced) and aspect ratio>16:9(e.g., wide screen with cinema scope size)”.

When the component type is “0xA1”, it indicates, e.g., that “video=480progressive (or 525 progressive) and aspect ratio=4:3”. When thecomponent type is “0xA3”, it indicates, e.g., that “video=480progressive (or 525 progressive), aspect ratio=16:9, and panvector=none”. When the component type is “0xA4”, it indicates, e.g.,that “video=480 progressive (or 525 progressive) and aspect ratio>16:9(e.g., wide screen with cinema scope size)”.

When the component type is “0xB1”, it indicates, e.g., that “video=1080interlaced (or 1125 interlaced) and aspect ratio=4:3”. When thecomponent type is “0xB3”, it indicates, e.g., that “video=1080interlaced (or 1125 interlaced), aspect ratio=16:9, and panvector=none”. When the component type is “0xB4”, it indicates, e.g.,that “video=1080 interlaced (or 1125 interlaced) and aspect ratio>16:9(e.g., wide screen with cinema scope size)”.

FIGS. 40 and 41 are flow charts (overall transfer operation flow) forexplaining an example of the overall data transfer operation in theapparatus shown in FIG. 20. Steps ST300 to ST312 in FIG. 40 are the sameprocesses as those in steps ST200 to ST212 shown in FIG. 30 above. Instep ST314 in FIG. 40, the PID to be played back is determined based onthe PMT, and is set in decoder unit 59. Also, STC 102 is reset, and atransfer setup is made in decoder unit 59. After that, a process uponcell transfer starts (step ST320). Steps ST320 to ST346 in FIG. 41 arethe same processes as those in steps ST220 to ST246 in FIG. 31 above. InFIG. 41, however, processes corresponding to steps ST234 to ST239 inFIG. 31 are not executed.

As can be seen from comparison between FIGS. 30 and 31 and FIGS. 40 and41, a process for externally transferring data is substantially the sameas a normal playback process, except for the following difference incontents. That is, in the process shown in FIGS. 40 and 41, TS packettransfer unit 101 calculates the transfer time based on the ATS in apack group and outputs TS packets within a time corresponding to thecalculated transfer time in the cell playback process. Also, the PCR isread out based on PCR location information to adjust the time of STC 102(STC reset in step ST314), thus synchronizing internal clocks (STC) andexternal clocks (PCR). In this manner, the user can designate a playbackpoint on a time basis in the cell playback process of data recorded bystream recording.

FIGS. 42 and 43 are flow charts (process flow upon cell transfer) forexplaining an example of the process upon cell transfer (ST320) shown inFIG. 41. Steps ST3200 to ST3214 in FIG. 42 are the same processes asthose in steps ST2200 to ST2214 in FIG. 32 above. Also, steps ST3216 toST3238 in FIG. 43 are the same processes as those in steps ST2216 toST2238 in FIG. 33 above, except for steps ST3217 to ST3224.

Steps ST3216 to ST3238 in FIG. 43 are processed by decoder unit 59 inFIG. 20. The PCR location is detected based on PCR information 156 inpack group header 161 shown in FIG. 14 and the like, and that PCR isread out onto register 2 (not shown). The PCR in register 2 is comparedwith the count value of STC 102. If they are different, the count value(corresponding to the playback time) of STC 102 is corrected (stepST3217). Next, ATS 151 in pack group header 161 is read out ontoregister 1 (not shown). The ATS in register 1 is compared with the countvalue of STC 102. If they match, the first TS packet is transferred(step ST3219). After that, the next IAPAT is read out and is added tothe contents of register 1 (not shown). The sum is compared with thecount value of STC 102, and when the two values match, the next TSpacket is transferred (step ST3221).

To summarize the above description, the calculation associated with TSpacket output can be made by the following method. That is, the first TSpacket in a pack group is output when the ATS in the header matches theSTC value. As for the second and subsequent TS packets, the sum of theATS and IAPAT immediately before the TS packet of interest is comparedwith the value of STC 102, and the packet of interest is output whenthey match.

The above processes (steps ST3217 to ST3221) are repeated 85 times (NOin step ST3223) in case of pack group 140 shown in FIG. 14. Uponcompletion of transfer of 85 TS packets (YES in step ST3223), the nextprocess in step ST3224 (the same process as in step ST2224 in FIG. 33)is executed. The subsequent processes are the same as those in FIG. 33.

FIG. 44 is a flow chart (process flow upon time search) for explainingan example of a time search process (a search conducted based on aplayback time designated by the user) with respect to the alreadyrecorded stream information of a digital TV broadcast program or thelike in the apparatus shown in FIG. 20.

<01> The user selects and determines a target title, playback starttime, stream number (1 in case of one stream) (step ST400).

<02> Program chain PGC, programs PG, and cells to be played back aredetermined based on the information of user's choice, and correspondingprogram chain information PGCI, program information PGI, and cellinformation CI are read out from management information (PGCI in FIG.10) (steps ST402 to ST404).

<03> ESOBI to be played back is determined based on a corresponding ESOBnumber (FIG. 11 or 13) in readout cell information CI (step ST406).Also, a map group number (e.g., MAP_Group#n in FIG. 6) in the ESOBI(e.g., ESOBI#1 in FIG. 6) to be played back is determined based on thestream number in the readout management information (ESFIT in FIG. 4)(step ST408).

<04> After a map group is determined in correspondence with the abovemap group number, a map group entry which is closest to the playbacktime and has a value smaller than the playback time is determined, andinformation (FIG. 7) of a map entry is read out (step ST410). Note thatmap group entries are assured at 10-sec intervals (as in videorecording).

<05> A corresponding ESOBU entry (e.g., ESOBU_ENT#1 in FIG. 8) is readout based on the ESOBU number (ESOBU_ENT_NUMs in FIG. 7) in the mapentry information. The ESOBU playback time (ESOBU_PB_TM in FIG. 8; thenumber of frames) is added to the playback time in the map group entryinformation to determine an ESOBU entry which is closest to the targetplayback time and has a value smaller than the target playback time(step ST412).

At this time, respective ESOBU sizes (ESOBU_SZ in FIG. 8) to a targetESOBU are summed up on the basis of ESOBU address information in the mapentry information and ESOBU data designated by the map entryinformation, thus calculating an ESOBU address (step ST414).

<06> An address from which playback is to start is calculated on thebasis of the address of a reference picture (I-picture) in the targetESOBU entry information and the target ESOBU address (step ST416). Atthis time, if a pack group header (FIG. 14) includes PCR information,the pack group header is read out.

<07> A PCR address is calculated based on the PCR information to loadthe PCR, and the PCR is set in STC 102 (step ST418).

<08> Decoder unit 59 undergoes a decode initial setup process (stepST420) to set a display start time to be a target playback time.

<09> An instruction is issued to disc drive unit 51 to read out recordeddata from the address calculated in step ST414, thus starting a dataread process.

<10> After playback starts, the control then enters a normal playbackprocess (e.g., a cell playback process in FIGS. 32 and 33 and the like).

The process in FIG. 44 is an example of special playback on a playbacktime basis in stream recording, which can be implemented since the datastructure of the present invention has PCR location information (156 inFIG. 14 and/or 132234 in FIG. 8).

FIG. 45 is a view for explaining another example of the configuration ofa data unit (ESOBU) for the stream object (ESOB). The data structure ofFIG. 45 may be used in place of that of FIG. 14. In the data structureof FIG. 45, extended stream object ESOB 132 is formed of a plurality ofextended stream object unit ESOBU 134 (see FIG. 45(a)(b)). Each ESOBU134 includes one or more packet groups 140 (see FIG. 45(b)(c)). Here,the boundary between adjacent ESOBUs (e.g., the boundary between ESOBU#1and ESOBU#2, and/or that between ESOBU#2 and ESOBU#3) may not becorresponding to the boundary between adjacent packet groups 140. Inother words, in the example of FIG. 45, ESOBU#2 are not aligned to anyof packet groups 140 (see FIG. 45(b)(c)).

Each packet group 140 corresponds to a plurality of logical blocks 139.In the example of FIG. 45(c)(d)(e), one packet group 140 corresponds to16 logical blocks. The size of one packet group 140 may be correspondingto a playback time of one or more seconds. Packet group 140 is formed ofpacket group header 161 and a subsequent pairs of time stamp items(PATS) 163 a and packets (MPEG-TS) 162. In the example of FIG. 45, onepacket group 140 includes one packet group header 161 and 170 pairs ofPATSs 163 a and packets 162 (see FIG. 45(e)(f)).

Packet group header 161 is configured to include header identifierHEADER_ID, packet group general information PKT_GRP_GI, display controlinformation and copy control information DCI_CCI, and manufacturer'sinformation MNFI (FIG. 45(g)). Packet group general informationPKT_GRP_GI is configured to include packet group type informationPKT_GRP_TY, and packet group version information VERSION (FIG. 45(h)).

FIG. 46 is a view for explaining another example of the configuration ofmanagement information (EHDVR_MG) recorded on AV data managementinformation recording area 130 shown in FIG. 1. The data structure ofFIG. 46 may be used in place of (or may be used with) that of FIG. 3 toFIG. 13. In the data structure of FIG. 46, extended high definitionvideo recording manager EHDVR_MG is configured to include extended highdefinition video recording manager information EHDVR_MGI, extended movieAV file information table EM_AVFIT, extended still picture AV fileinformation table ES_AVFIT, extended stream file information tableESTR_FIT, extended original program chain information EORG_PGCI,extended user defined program chain information table EUD_PGCIT (whichis necessary when at least one extended user defined PGC exists),extended text data manager ETXTDT_MG, extended manufacturer'sinformation table EMNFIT, extended video time amp information tableEVTMAPIT, and extended stream time map information table ESTMAPIT (FIG.46(a)(b)).

Extended high definition video recording manager information EHDVR_MGIis configured to include extended video manager information managementtable EVMGI_MAT, and extended play list search pointer table EPL_SRPT(FIG. 46(b)(c)). Extended play list search pointer table EPL_SRPT isconfigured to include extended play list search pointer tableinformation EPL_SRPTI, and one or more extended play list searchpointers #1 to #n (FIG. 46(c)(d)).

FIG. 47 exemplifies contents of the extended video manager informationmanagement table (VMGI_MAT) shown in FIG. 46. Extended video managerinformation management table VMGI_MAT is configured to include extendedvideo manager identifier VMG_ID, end address EHR_MANGR_EA of thosenavigation data recorded in control information file EHR_MANGR.IFO, andend address EHDVR_MGI_EA of EHDVR_MGI. VMGI_MAT is configured to furtherinclude version number VERN of the Book, time zone TM_ZONE, still timeSTILL_TM for still pictures, character set code CHRS for a primary text,resume marker information RSM_MRKI, disc representative pictureinformation DISC_REP_PICTI, disc representative name DISC_REP_NM, startaddress EM_AVFIT_SA of the extended movie AV file information table, andstart address ES_AVFIT_SA of the extended still AV file informationtable.

VMGI_MAT is configured to further include encrypted title keyinformation ETKI, copy protection scheme information CPSI, and startaddress ESTR_FIT_SA of the extended stream file information table.VMGI_MAT is configured to further include start address EORG_PGCI_SA ofthe extended original PGC information, start address EUD_PGCIT_SA of theextended user-defined PGC information table, start address TXTDT_MG_SAof the extended text data manager, start address EMNFIT_SA of theextended manufacturer's information table, last modification timeEVTMAP_LAST_MOD_TM of the extended video time map, and last modificationtime ESTMAP_LAST_MOD_TM of the extended still time map.

FIG. 48 exemplifies contents of the extended play list search pointer(EPL_SRP) shown in FIG. 46. Extended play list search pointer EPL_SRP isconfigured to include PGC number PGCN, play list creating timePL_CREATE_TM, primary text information PRM_TXTI, item text searchpointer number IT_TXT_SRPN for this play list, representative pictureinformation REP_PICTI, extended play list resume marker informationEPL_RSM_MRKI, extended play list index EPL_INDEX, and extended play listlast modification time EPL_LAST_MOD_TM.

FIG. 49 exemplifies contents of the play list resume marker information(EPL_SRP) shown in FIG. 46. Play list resume marker information EPL_SRPis configured to include cell number CN (describing the cell number inwhich the picture point exists), picture point PICT_PT (describing thepicture point in the target cell), and marking time MRK_TM (describingthe time when this marker was made).

FIG. 50 exemplifies contents of the extended movie AV file informationtable (EM_AVFIT) shown in FIG. 46. Extended movie AV file informationtable EM_AVFIT is configured to include extended movie AV fileinformation table information EM_AVFITI, one or more extended movievideo object stream information EM_VOB_STI#1 to EM_VOB_STI#n, andextended movie AV file information EM_AVFI (FIG. 50(a)(b)). Extendedmovie AV file information EM_AVFI is configured to include EM_AVFIgeneral information EM_AVFI_GI, one or more EM_VOBI search pointersEM_VOBI_SRP#1 to EM_VOBI_SRP#n, and one or more extended movie VOBinformation EM_VOBI#1 to EM_VOBI#n (FIG. 50(b)(c)). Each EM_VOBI isconfigured to include extended movie VOB general information EM_VOB_GI,extended seamless information ESMLI, extended audio gap informationEAGAPI, and extended VOB time map information EVOB_TMAPI (FIG.50(c)(d)). This EVOB_TMAPI may comprise extended VOB time map generalinformation EVOB_TMAP_GI (FIG. 50(d)(e)).

FIG. 51 exemplifies contents of the extended movie video object generalinformation (EM_VOB_GI) shown in FIG. 50. Extended movie video objectgeneral information EM_VOB_GI is configured to include VOB type VOB_TY,recording time VOB_REC_TM of this VOB, sub-second informationVOB_REC_TM_SUB for VOB_REC_TM, M_VOB_STI number M_VOB_STIN, video startpresentation time VOB_V_S_PTM of this VOB, video end presentation timeVOB_V_E_PTM of this VOB, and time zone LOCAL_TM_ZONE wherein the VOB hasbeen originally recorded and VOB_REC_TM as well as VOB_REC_TM_SUB havebeen recorded.

FIG. 52 exemplifies contents of the extended video object time mapgeneral information (EVOB_TMAP_GI) shown in FIG. 50. Extended videoobject time map general information EVOB_TMAP_GI is configured toinclude number VOBU_ENT_Ns of the VOBU entries, address offset ADR_OFS,and playback time range VOBU_PB_TM_RNG of VOBU. One or more playbacktime ranges can be specified by VOBU_PB_TM_RNG. For instance, whenVOBU_PB_TM_RNG=00h, the playback time range is 0.4 to 1.0 second. IfVOBU_PB_TM_RNG is 01h, the playback time range may be, e.g., 1.0 to 2.0seconds. Other time ranges can be specified by VOBU_PB_TM_RNG=10h or 11h.

FIG. 53 exemplifies contents of the extended still picture AV fileinformation table (ES_AVFIT) shown in FIG. 46. Extended still picture AVfile information table ES_AVFIT is configured to include extendedS_AVFIT information ES_AVFITI, one or more extended still picture VOBstream information ES_VOB_STI#1 to ES_VOB_STI#n, extended still pictureAV file information ES_AVFI, one or more extended still pictureadditional audio stream information ES_AA_STI#1 to ES_AA_STI#m, andextended still picture additional audio file information ES_AAFI (FIG.53(a)(b)). Extended still picture AV file information ES_AVFI isconfigured to include ES_AVFI general information ES_AVFI_GI, one ormore extended still picture video object group information searchpointers ES_VOGI_SRP#1 to ES_VOGI_SRP#n, and one or more extended stillpicture video object group information ES_VOGI#1 to ES_VOGI#n (FIG.53(b)(c)).

Each ES_VOGI is configured to include extended still picture videoobject group general information ES_VOG_GI, and one or more extendedstill picture VOB entries ES_VOB_ENT#1 to ES_VOB_ENT#n (FIG. 53(c)(d)).Here, ES_VOG_GI is configured to include number S_VOB_Ns of S_VOBS,S_VOB_STI number S_VOB_STIN, recording time of the first video objectFIRST_VOB_REC_TM, recording time of the last video objectLAST_VOB_REC_TM, start address of the still picture video object groupS_VOG_SA, and time zone LOCAL_TM_ZONE of this S_VOG (FIG. 53(d)(e)).

FIG. 54 exemplifies contents of the extended stream file informationtable (ESTR_FIT) shown in FIG. 46. Extended stream file informationtable ESTR_FIT is configured to include extended stream file informationtable information ESTR_FITI, one or more extended stream fileinformation search pointers ESTR_FI_SRP#1 to ESTR_FI_SRP#n, and one ormore extended stream file information ESTR_FI#1 to ESTR_FI#n (FIG.54(a)(b)). Extended stream file information table information ESTR_FITIis configured to include number ESTR_FI_Ns of ESTR_FI, and end addressESTR_FIT_EA of ESTR_FIT (FIG. 54(b)(c)). Extended stream fileinformation search pointer ESTR_FI_SRP is configured to include startaddress ESTR_FI_SA of ESTR_FI, and size ESTR_FI_SZ of ESTR_FI (FIG.54(b) (d)).

Extended stream file information ESTR_FI is configured to includeESTR_FI general information ESTR_FI_GI, one or more extended streamobject information search pointers ESOBI_SRP#1 to ESOBI_SRP#n, and oneor more extended stream object information ESOBI#1 to ESOBI#n (FIG.54(b)(e)). Extended stream object information ESOBI is configured toinclude ESOBI general information ESOBI_GI, one or more extended streamobject elementary stream information ESOB_ESI#1 to ESOB_ESI#n, areserved are for ESOB seamless information, extended stream objectgrouping information ESOB_GPI, and extended stream object time mapinformation ESOB_TMAPI (FIG. 54(e)(f)).

FIG. 55 exemplifies contents of the extended stream object information(ESOBI) shown in FIG. 54. Extended stream object information ESOBI isconfigured to include ESOBI_GI, ESOB_ESI#1 to ESOB_ESI#n, ESOB seamlessinformation reserved area, ESOB_GPI, and ESOB_TMAPI (FIG. 55(e)(f)).ESOB_GI is configured to include ESOB_GPI general informationESOB_GPI_GI, one or more grouping information search pointers GPI_SRP#1to GPI_SRP#n, and one or more grouping information GPI #1 to GPI #n(FIG. 55(f)(g)). ESOB_GPI_GI is configured to include number GPI_SRP_Nsof the GPI search pointers (FIG. 55(g)(h)). Each GPI search pointerGPI_SRP is configured to include start address GPI_SA of GPI (FIG.55(g)(i)). Each GPI is configured to include GPI general informationGPI_GI, and one or more elementary stream PID ES_PID#1 to ES_PID#n (FIG.55(g)(j)). Meanwhile, ESOB_TIMAPI is configured to include extendedstream object time map general information ESOB_TMAP_GI, and one or moreextended elementary stream time map general information EES_TMAP_GI#1 toEES_TMAP_GI#n (FIG. 55(f)(k)).

FIG. 56 exemplifies contents of the extended stream object informationgeneral information (ESOBI_GI) shown in FIG. 55. Extended stream objectinformation general information ESOBI_GI is configured to includeextended stream object type ESOB_TY, application format name (minor)APP_FORMAT2, profile ESOB_PROFILE of this ESOB, PID of PMT packetPMT_PID, PCR of PCR packet PCR_PID, original network identifierNETWORK_ID, transport stream identifier TS_ID, program number (serviceidentifier) PROGRAM_NUMBER, ID of registration descriptor FORMAT_ID,service type SERVICE_TYPE, copy control information CP_CTRL_INFO,recording time ESOB_REC_TM of this ESOB, sub-second informationESOB_REC_TM_SUB for ESOB_REC_TM, local time zone LOCAL_TM_ZONE, defaultPID “ESOB_DEF PID” of this ESOB, start presentation time “ESOB_S_PTM” ofthis ESOB, end presentation time “ESOB_E_PTM” of this ESOB, durationESOB_DURATION of this ESOB, number (PCR_POS_COUNT) of the preceding PCRpackets indicated by PCR_POS, bit shift (PCR_POS_SHIFT) of PCR_POS forthe designated PCR packet, number ESOB_ES_Ns of elementary streams inthis ESOB, number ESOB_V_ES_Ns of video elementary streams in this ESOB,and number ESOB_A_ES_Ns of audio elementary streams in this ESOB.

FIG. 57 exemplifies contents of the extended stream object type(ESOB_TY) shown in FIG. 56. Extended stream object type ESOB_TY isconfigured to include a reserved bit field followed by a temporarilyerased state flag (TE flag), a grouping information flag (GPI flag),another reserved bit field, and a seamless flag (SML flag). Here, the TEflag may be used to indicate whether the corresponding ESOB is in anormal state or in a temporarily erased state. An ESOB in thetemporarily erased state will not be referred to by a cell in a userdefined PGC. An ESOB in the temporarily erased state will not bereproduced in a normal playback operation. The GPI flag may be used toindicate whether the corresponding ESOB is provided with an ESOBelementary stream grouping information.

FIG. 58 exemplifies contents of the copy control information(CP_CTRL_INFO) shown in FIG. 56. Copy control information CP_CTRL_INFOis configured to include a CCI field, an APS field, an EPN field, an ICTfield, a retention fled, a retention state field, and reserved field.Bits of the CCI field may be used to specify a copy-free, no more copy,copy one generation (copy once), or copy never. Bits of the APS (analogprotection system) field may be used to specify a copy-free, a type 1APS is on (automatic gain control AGC), a type 2 APS is on (AGC+2L colorstripe), or a type 3 APS is on (AGC+4L color stripe). A bit of the EPNfield may be used to specify an EPN-asserted state, or an EPN-unassertedstate. When the EPN-asserted state is specified, contents of thecorresponding ESOB are prevented from being output (especiallyinternet-output). When the EPN-unasserted state is specified, contentsof the corresponding ESOB are not prevented from being output. A bit ofthe ICT (image constraint token) field may be used to specify a highdefinition analog output in the form of a constraint image, or a highdefinition analog output in a high definition analog form. A bit of theretention field may be used, with a combination of the CCI field, tospecify a movie mode (retention=0b and CCI=10b), a retention mode(retention=0b and CCI=11b), a non-movie mode/non-retention mode(retention=0b and CCI=00b or 01b), or a non-movie mode/non-retentionmode (retention=1b). Bits of the retention state field may be used tospecify the retention time forever, the retention time one week, theretention time two days, the retention time one day, the retention time12 hours, the retention time 6 hours, the retention time 3 hours, or theretention time 90 minutes.

FIG. 59 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for video ES) shown in FIG. 55. Extended streamobject elementary stream information ESOB_ESI for video ES is configuredto include type ES_TY of the elementary stream, PID of the elementarystream ES_PID, stream type STREAM_TYPE in PMT, component tagCOMPONENT_TAG in the stream identifier descriptor, stream contentSTREAM_CONTENT in the component descriptor, component typeCOMPONENT_TYPE in the component descriptor, attributes of video V_ATR,and copy control information CP_CTRL_INFO.

FIG. 60 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for audio ES) shown in FIG. 55. Extended streamobject elementary stream information ESOB_ESI for audio ES is configuredto include type ES_TY of the elementary stream, PID of the elementarystream ES_PID, stream type STREAM_TYPE in PMT, component tagCOMPONENT_TAG in the stream identifier descriptor, stream contentSTREAM_CONTENT in the component descriptor/audio component descriptor,component type COMPONENT_TYPE in the component descriptor/audiocomponent descriptor, simulcast group tag SIMULCAST_GP_TAG in the audiocomponent descriptor, attributes of audio elementary stream A_ATR, audiolanguage code LANG_CODE, second audio language code LANG_CODE2, and copycontrol information CP_CTRL_INFO.

FIG. 61 exemplifies contents of extended stream object elementary streaminformation (ESOB_ESI for other ES) shown in FIG. 55. Extended streamobject elementary stream information ESOB_ESI for other ES is configuredto include type ES_TY of the elementary stream, PID of the elementarystream ES_PID, stream type STREAM_TYPE in PMT, component tagCOMPONENT_TAG in the stream identifier descriptor, data component ID“DAT_COMP_ID” in the data component descriptor or data contentdescriptor for this other elementary stream in case of the ARIBstandard, additional data component information “AD_DAT_COMP_IFO” in thedata component descriptor for this other elementary stream in case ofthe ARIB standard, and copy control information CP_CTRL_INFO.

FIG. 62 exemplifies contents of stream type information (ES_TY) shown ineach of FIGS. 59 to 61. Stream type information ES_TY is configured toinclude a field of stream type ST_TY. Bits of the ST_TY field may beused to specify the video elementary stream, audio elementary stream, orother elementary stream.

FIG. 63 exemplifies contents of the video attribute information (V_ATR)shown in FIG. 59. Video attribute information V_ATR is configured toinclude an application flag field, an aspect ratio field, a reservedfield, a horizontal resolution field, another reserved field, a framerate field, a vertical resolution field, and still another reservedfield. Here, bits of the application flag field can be used to specify afirst state in which the video stream is coded with the aspect ratiospecified in the V_ATR, and a second state in which the video stream maybe coded with the aspect ratio specified in the V_ATR. In the secondstate, the actual aspect ratio may be recorded in the correspondingstream. The bits of the application flag field can also be used tospecify other (reserved) state.

FIG. 64 exemplifies contents of the audio attribute information (A_ATR)shown in FIG. 60. Audio attribute information A_ATR is configured toinclude a multi-lingual field (multi_ling), a main component field(main_comp), a quality indicator field (quality_indicator), a samplingrate field (sampling_rate), and a reserved field. Here, a bit of themulti-lingual field may be used to specify a no multi-lingual audiostream, or a bi-lingual audio stream in case where the stream is a dualmono. A bit of the main component field may be used to specify a case inwhich the audio stream is not a main audio, or another case in which theaudio stream is the main audio. Bits of the quality indicator field maybe used to specify a reserved state, a mode 1 state, a mode 2 state, ora mode 3 state (note that the mode 1 state to mode 3 state may bedefined according to a digital broadcasting standard such as “ARIBSTD-B32 Part 2, Chapter 2.”) Bits of the sampling rate field may be usedto specify a sampling frequency of 16 kHz, 22.05 kHz, 24 kHz, 32 kHz,44.1 kHz, or 48 kHz.

FIG. 65 exemplifies contents of the grouping information generalinformation (GPI_GI) shown in FIG. 55. Grouping information generalinformation GPI_GI is configured to include type BLOCK_TY of a block ofgroups, type GP_TY of an ES group, block number BLOCK_NUMBER, and numberof the ES_PIDs “ES_PID Ns.” Here, bits of BLOCK_TY may be used tospecify a no definition state, a multi-view state, a rain attenuationstate, a multi-channel state, or other reserved states. Bits of GP_TYmay be used to specify no definition, a main group, a sub-group, orother reserved ones. The range of BLOCK_NUMBER may be any of 1 to 32.The range of ES_PID_Ns may be any of 1 to 32.

FIG. 66 exemplifies contents of the elementary stream packet identifier(ES_PID) shown in FIG. 55. Elementary stream packet identifier ES_PID isconfigured to include a PID of elementary stream “ES_PID.” This ES_PIDdescribes the PID of the elementary stream belonging to thecorresponding group.

FIG. 67 exemplifies contents of the extended stream object time mapgeneral information (ESOB_TMAP_GI) shown in FIG. 55. Extended streamobject time map general information ESOB_TMAP_GI is configured toinclude address offset ESOB_ADR_OFS of the ESOB, size ESOB_SZ of theESOB, ESOB start packet position ESOB_S_PKT_POS, ESOB end packetposition ESOB_E_PKT_POS, playback time range ESOBU_PB_TM_RNG of theESOBU, and number EES_TMAP_GI_Ns of the extended elementary stream timemap general information items (EES_TMAP_GIs).

Here, ESOB_ADR_OFS may be used to indicate the start address of thecorresponding ESOB from the first logical block of an extendedhigh-resolution stream video recording object file (EHR_STRxx.VRO file;not shown). ESOB_SZ may be used to indicate the size of thecorresponding ESOB with the number of packet groups. In other words, thesize of ESOB may be described in unit of a packet group.

ESOB_S_PKT_POS may be used to indicate the start packet position of thecorresponding ESOB from the first packet group of this ESOB, where thevalue of ESOB_S_PKT_POS may be any of 1 to PKT_Ns. ESOB_E_PKT_POS may beused to indicate the end packet position of the corresponding ESOB fromthe last packet group of this ESOB, where the value of ESOB_E_PKT_POSmay be any of 1 to PKT_Ns.

ESOBU_PB_TM_RNG may be used to indicate the playback time range of thecorresponding ESOBU. More specifically, when ESOBU_PB_TM_RNG=00h, theplayback time range may be 0.4 to 1.0 second, for example. IfESOBU_PB_TM_RNG is 01h, the playback time range may be, e.g., 1.0 to 2.0seconds, for example. Other time ranges may be specified byESOBU_PB_TM_RNG=10 h or 11 h.

EES_TMAP_GI_Ns may be used to indicate the number of extended elementarystream time map general information items (EES_TMAP_GIs) for thecorresponding ESOB. EES_TMAP_GI_Ns (corresponding to the number ofEES_TMAP_GI#1 to EES_TMAP_GI#n in FIG. 55(k)) is selected to be the sameas the number (ETMAPI_Ns described in, e.g., extended HR_STMAP.IFO file:not shown) of extended elementary time map information items(corresponding to ESTMAPI#1 to ESTMAPI#n in FIG. 74(b)).

FIG. 68 exemplifies contents of the extended elementary stream time mapgeneral information (EES_TMAP_GI) shown in FIG. 55. Extended elementarystream time map general information EES_TMAP_GI is configured to includeelementary stream PID “ES_PID”, start presentation time “ES_S_PTM” ofthe corresponding elementary stream, end presentation time “ES_E_PTM” ofthe corresponding elementary stream, start address offset “ES_S_ADR_OFS”for the corresponding elementary stream, last ESOBU end packet position“ES_LAST_ESOBU_E_PKT_POS”, and number “ES_ESOBU_ENT_Ns” of ESOBU entriesfor the corresponding elementary stream.

Here, ES_PID may be used to indicate the PID (packet identifier) of avideo elementary stream for which the corresponding time map isgenerated. ES_S_PTM may be used to indicate the presentation start time(coded as presentation time stamp PTS) of the first video field of thecorresponding elementary stream. ES_E_PTM may be used to indicate thepresentation terminating time of the last video field of thecorresponding elementary stream. ES_S_ADR_OFS may be used to indicatethe start address of the corresponding elementary stream, with thenumber of packet groups from the first packet group of the ESOB.ES_LAST_ESOBU_E_PKT_POS may be used to indicate the end packet positionof the last ESOBU, with the packet number (e.g., any one of 1 to 170 inthe embodiment of FIG. 45(f)), in the last packet group of thecorresponding ESOB. ES_ESOBU_ENT_Ns may be used to indicate the numberof ESOBU entries (which are included in, e.g., the extended HR_STMAP.IFOfile, not shown) in the extended stream time map information of thecorresponding elementary stream.

FIG. 69 exemplifies contents of the extended program chain information(EPGCI; or extended original PGC information EORG_PGCI) shown in FIG.46. Extended program chain information EPGCI is configured to includeextended program chain general information (EPGC_GI), extended programinformation #1 (EPGI#1) to extended program information #m (EPGI#m),extended cell information search pointer #1 (ECI_SRP#1) to extended cellinformation search pointer #n (ECI_SRP#n), and extended cell information#1 (ECI#1) to extended cell information #n (ECI#n) (FIG. 69(a)(b)). Eachof ECI_SRP#1 to ECI_SRP#n may include start address ECI_SA of thecorresponding ECI (FIG. 69(b)(c)). Incidentally, EPGCI is extendedmanagement information for managing PGC which comprises one or moreprograms each including one or more cells.

Here, there are three types of the extended cell information ECI; moviecell information M_CI, still picture cell information S_CI, and extendedstream cell information ESTR_CI (FIG. 69(b)(d)). The data structure ofM_C₁ and S_CI may be substantially the same as those of the current DVDVideo Recording standard. Meanwhile, the data structure of ESTR_CIdiffers therefrom. More specifically, ESTR_CI is configured to includeextended stream cell general information ESTR_C_GI, and one or moreextended stream cell entry point information items #1 to #n(ESTR_C_EPI#1 to ESTR_C_EPI#n) (FIG. 69(d)(e)). Extended stream cellgeneral information ESTR_C_GI may be configured to include cell typeC_TY, stream file number ESTR_FN, extended stream object informationsearch pointer number ESOBI_SRPN, number C_EPI_Ns of the C_EPIs, startPTM “C_S_PTM” of the corresponding cell, end PTM “C_E_PTM” of thecorresponding cell, and default PID of the corresponding cell (FIG.69(e)(f)).

FIG. 70 exemplifies contents of the extended program chain generalinformation (EPGCI_GI) shown in FIG. 69. Extended program chain generalinformation EPGCI_GI is configured to include number PG_Ns of theprograms in the corresponding extended PGC, and number CI_SRP_Ns of theextended CI_SRPs in the corresponding extended PGC. In case of theextended user defined PGC, this PG_Ns is set to ‘0’. In case of theextended original PGC, this PG_Ns may be any one of 1 to 99. The maximumnumber of this CI_SRP_Ns may be ‘1998’ which is the sum of ‘999’ formovie cells and ‘999’ for still picture cells.

FIG. 71 exemplifies contents of the extended program information (EPGI)shown in FIG. 69. Extended program information EPGI is configured toinclude program type PG_TY, number C_Ns of the cells in thecorresponding program, primary text information PRM_TXTI for thisprogram, item text information search pointer number IT_TXT_SRPNindicating an item text whose text data may correspond to this program,representative picture information REP_PICTI, program resume markerinformation PG_RSM_MRKI, program index PG_INDEX, and program lastmodification time PG_LAST_MOD_TM describing the time when thecorresponding program was modified last.

Here, PG_TY may be used to include protect information indicatingwhether the corresponding program is in a protected state. If theprogram is in the protected state, all data object referred to and usedin the presentation (playback) of the program should not be erasedtemporarily or permanently.

REP_PICTI may be used to include cell number CN and picture pointPICT_PT. The CN may describe the cell number in which the correspondingpicture point (PICT_PT) exists. The PICT_PT may indicate the picturepoint in the target cell, using the presentation time (PTM).

PG_INDEX may be used to indicate the index number of the correspondingprogram. PG_INDEX is a unique number assigned to each program. Two ormore programs should not have the same PG_INDEX value. Whenever creatinga new program, unused available index value may be searched anddescribed in PG_INDEX. The value of PG_INDEX may be kept unchanged untilthe corresponding program is deleted. The value of PG_INDEX may be keptunchanged when the corresponding program is modified. The value ofPG_INDEX may be kept unchanged when other programs are deleted and/ornewly created.

FIG. 72 exemplifies contents of the program resume marker information(PG_RSM_MRKI) shown in FIG. 71. Program resume marker informationPG_RSM_MRKI is configured to include cell number CN, picture pointPICT_PT, and marking time MRK_TM. The CN may describe the cell number inwhich the picture point (PICT_PT) exists. The PICT_PT may describe thepicture point in the target cell. The MRK_TM may describe the time whenthe corresponding marker was made. In short, PG_RSM_MRKI may be used toinclude a resume marker of the corresponding program. PG_RSM_MRKI shouldnot refer to the data object in a temporarily erased state.

FIG. 73 exemplifies contents of the extended video time map informationtable (EVTMAPIT) shown in FIG. 46. Extended video time map informationtable EVTMAPIT is configured to include video time map information tableinformation VTMAPITI, one or more video time map information searchpointers #1 to #n (VTMAPI_SRP#1 to VTMAPI_SRP#n), and one or more videotime map information items #1 to #n (VTMAPI#1 to VTMAPI#n) (FIG.73(a)(b)).

Here, VTMAPITI may be used to include video manager identifier VMG_ID,end address VTMAPIT_EA of video time map information table VTMAPIT,version number VERN of the used standard (e.g., DVD EHD_VR standard),last modification time VTMAP_LAST_MOD_TM of video time map VTMAP, andnumber VTMAPI_SRP_Ns of video time map information search pointers (FIG.73(b)(c)). VMG_ID may be used to describe “DVD_EHR_VTMAP” to identify avideo time map file (EHR_VTMAP.IFO; not shown) with character set codeof ISO/IEC 646:1983. VTMAP_LAST_MOD_TM may be used to describe the timewhen the content of EHR_VTMAP.IFO was modified last.

Each VTMAPI_SRP may include start address VTMAPI_SA of VTMAPI, andnumber VOBU_ENT_Ns of VOBU entries shown in FIG. 73 (e) (FIG. 73(b)(d)).Each VTMAPI may include one or more VOBU entries #1 to #q (VOBU_ENT#1 toVOBU_ENT#q) (FIG. 73(b)(e)). Each VOBU_ENT may include first referencepicture size 1ST_REF_SZ of the corresponding video object unit VOBU,playback time VOBU_PB_TM of the corresponding VOBU, and size VOBU_SZ ofthe corresponding VOBU (FIG. 73(e)(f)).

FIG. 74 exemplifies contents of the extended stream time map informationtable (ESTMAPIT) shown in FIG. 46. Extended stream time map informationtable ESTMAPIT is configured to include extended stream time mapinformation table information ESTMAPITI, one or more extended streamtime map information search pointers #1 to #n (ESTMAPI_SRP#1 toESTMAPI_SRP#n), and one or more extended stream time map informationitems #1 to #n (ESTMAPI#1 to ESTMAPI#n) (FIG. 74(a)(b)).

Here, ESTMAPITI may be used to include extended video manager identifierEVMG_ID, end address ESTMAPIT_EA of the extended stream time mapinformation table, version number VERN of the used standard (e.g., DVDEHD_VR standard), last modification time ESTMAP_LAST_MOD_TM of extendedstream time map ESTMAP, and number ESTMAPI_SRP_Ns of extended streamtime map information search pointers (FIG. 74(b)(c)). EVMG_ID may beused to describe “DVD_EHR_STMAP” to identify a stream time map file(EHR_STMAP.IFO; not shown) with character set code of ISO/IEC 646:1983.ESTMAP_LAST_MOD_TM may be used to describe the time when the content ofEHR_STMAP.IFO was modified last.

Each ESTMAPI_SRP may include extended stream time map information searchpointer general information ESTMAPI_SRP_GI, and one or more extendedelementary time map information general information items #1 to #p(EETMAPI_GI#1 to EETMAPI_GI#p) (FIG. 74(b)(d)). Here, ESTMAPI_SRP_GI maybe used to include start address ESTMAPI_SA of ESTMAPI, and numberEETMAPI_Ns of extended elementary time map information items (EETMAPIsshown in FIG. 74(g)) (FIG. 74(d)(e)). Each EETMAPI_GI may be used toinclude number ESOBU_ENT_Ns of extended stream object unit entries(ESOBU_ENTs in FIG. 74(h)) (FIG. 74(d)(f)). Each ESTMAPI may includeextended elementary time map information items #1 to #p (EETMAPI#1 toEETMAPI#p) (FIG. 74(b)(g)). Each EETMAPI may be configured to includeone or more extended SOBU entries #1 to #q (ESOBU_ENT#1 to ESOBU_ENT#q)(FIG. 74(g)(h)).

Each ESOBU_ENT may be configured to include first reference picture size1ST_REF_SZ of the corresponding ESOBU, playback time ESOBU_PB_TM of thecorresponding ESOBU, size ESOBU_SZ of the corresponding ESOBU, and startpacket position ESOBU_S_PKT_POS of the corresponding ESOBU (FIG.74(h)(i)). This ESOBU_S_PKT_POS may be used to describe the start packetposition of the corresponding ESOBU, with the relative packet number(PKTG_RPKTN) in the first packet group of the corresponding ESOBU. Thevalue of ESOBU_S_PKT_POS may be any one of 1 to PKT_Ns (number ofpackets in the packet group).

Incidentally, the pack/packet group header may contain arrival timeinformation (ATS) and attribute information (PCRI) of the first TSpacket, and the pack/packet group data may contain differenceinformation (IAPAT) from the arrival time of the first TS packettogether with data of TS packets, or may contain time information items(PATS#) of corresponding TS packets.

Note that at least one of TS packets may have an adaptation fieldincluding a predetermined program clock reference (PCR), and thepack/packet group header may contain location information (156 in FIG.14) of the program clock reference (PCR).

Alternatively, an information recording medium to which the system of anembodiment of the present invention can be applied may also beconfigured as follows. More specifically, in a recording mediumconfigured to record a digital stream signal complying with an MPEGtransport stream and a video recording signal obtained by converting ananalog signal into a digital signal by MPEG encoding, this recordingmedium may have a management area and data area, and the data area canstore both the video recording signal and digital stream signal. Data ofthis digital stream signal can be separately recorded as a plurality ofobjects (ESOB). Each object contains data units (ESOBU). One data unitis made up of pack/packet groups each of which is formed by grouping aplurality of transport stream packets (TS packets). The pack/packetgroup is formed of a pack/packet group header and pack/packet group datacontaining TS packets having data of the digital stream signal.

On the other hand, the management area may contain cell information (CI)associated with cells as playback units, and attribute information(contained in ESFI in FIG. 4; PCR_Pack number or 1st_Ref_PIC_PTM in FIG.8) of the object (ESOB). This cell information (management informationlayer 10 in FIG. 2) can designate both data (VOB in FIG. 2) of the videorecording signal and the object (ESOB in FIG. 2) (VOB can be designatedby time information VOBU_PB_TM (not shown); ESOB can be designated bytime information ESOBU_PB_TM in FIG. 8). This cell information (CI#q inFIG. 11) can record number information (corresponding ESOB number inFIG. 11) used to designate the object (ESOB).

Note that at least one of TS packets may have an adaptation fieldincluding a predetermined program clock reference (PCR), and themanagement area may contain location information (PCR_Pack number orcorresponding 1st_Ref_PIC_PTM in FIG. 8) of the program clock reference.

An information recording method according to an embodiment of thepresent invention may be configured to record information on theaforementioned medium.

An information playback method according to an embodiment of the presentinvention may be configured to play back information from theaforementioned medium.

An information recording apparatus according to an embodiment of thepresent invention may be configured to record information on theaforementioned medium.

An information playback apparatus according to an embodiment of thepresent invention may be configured to play back information from theaforementioned medium.

Also, an apparatus according to an embodiment of the present inventioncan comprise a management data generation unit for generating amanagement map or the like used to manage stream data, a supportinformation appending unit for appending support information ofmanagement data in the generated management data, and a drive unit forrecording the generated management data.

Incidentally, in the embodiment of FIG. 20, when a stream recording(digital video input) is performed, encoder unit 79 is configured torecord the digital stream signal using an MPEG transport stream. On theother hand, when a video recording (analog video input) is performed,encoder unit 79 is configured to record a digital stream signal,obtained by converting an analog video input using A/D converter 84,using an MPEG program stream.

Note that the present invention is not limited to the aforementionedembodiments, and various modifications may be made without departingfrom the scope of the invention when it is practiced. The respectiveembodiments may be combined as needed as long as such combinations arepossible, and combined effects can be obtained in such case.Furthermore, the embodiments include inventions of various stages, andvarious inventions can be extracted by appropriately combining aplurality of disclosed required constituent elements. For example, evenwhen some required constituent elements are omitted from all requiredconstituent elements described in the embodiment, an arrangement fromwhich the required constituent elements are omitted can be extracted asan invention as long as the problems that have been discussed in theparagraphs of the problems to be solved by the invention, and theeffects that have been explained in the paragraphs of the effect of theinvention can be obtained.

As described in detail above, according to the present invention, dataof digital TV broadcast and the like can be flexibly managed.

1. (canceled)
 2. An information medium comprising one or more data areasconfigured to store object information, and a management area configuredto store management information for managing the object information,wherein one of said data areas is configured to record stream objectusing a stream object unit in which contained are packet groups eachincluding a packet group header and multiple pairs of packet arrivaltime information and MPEG transport stream packet, and the managementinformation to be stored in said management area includes program chaininformation which contains one or more program information items, one ormore cell information items, and one or more cell information searchpointers corresponding to the one or more cell information items, andone of said program information items includes program resume markerinformation which contains marking time information describing a timewhen a corresponding resume marker was made.
 3. A method of recordinginformation on an information medium comprising one or more data areasconfigured to store object information, and a management area configuredto store management information for managing the object information,wherein one of said data areas is configured to record stream objectusing a stream object unit in which contained are packet groups eachincluding a packet group header and multiple pairs of packet arrivaltime information and MPEG transport stream packet, and the managementinformation to be stored in said management area includes program chaininformation which contains one or more program information items, one ormore cell information items, and one or more cell information searchpointers corresponding to the one or more cell information items, andone of said program information items includes program resume markerinformation which contains marking time information describing a timewhen a corresponding resume marker was made, said method comprising:recording the stream object on the data area, and recording themanagement information on the management area.
 4. A method ofreproducing information from an information medium comprising one ormore data areas configured to store object information, and a managementarea configured to store management information for managing the objectinformation, wherein one of said data areas is configured to recordstream object using a stream object unit in which contained are packetgroups each including a packet group header and multiple pairs of packetarrival time information and MPEG transport stream packet, and themanagement information to be stored in said management area includesprogram chain information which contains one or more program informationitems, one or more cell information items, and one or more cellinformation search pointers corresponding to the one or more cellinformation items, and one of said program information items includesprogram resume marker information which contains marking timeinformation describing a time when a corresponding resume marker wasmade, said method comprising: reproducing the management informationfrom the management area, and reproducing the stream object from thedata area.
 5. A recording apparatus for recording information on theinformation medium as defined in claim 2, said apparatus comprising: afirst recorder configured to record the stream object on the data area,and a second recorder configured to record the management information onthe management area.
 6. A reproducing apparatus for reproducinginformation from the information medium as defined in claim 2, saidapparatus comprising: a first reproducer configured to reproduce themanagement information from the management area, and a second reproducerconfigured to reproduce the stream object from the data area.